From: "Matias Bjørling" <mb@lightnvm.io>
To: hans@owltronix.com
Cc: javier@javigon.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hans Holmberg <hans.holmberg@cnexlabs.com>
Subject: Re: [PATCH] lightnvm: pblk: stop taking the free lock in in pblk_lines_free
Date: Tue, 22 Jan 2019 20:48:58 +0100 [thread overview]
Message-ID: <a0bceb9f-4f8a-1b69-8ef3-f2bc0747a3b5@lightnvm.io> (raw)
In-Reply-To: <20190122101531.30893-1-hans@owltronix.com>
On 1/22/19 11:15 AM, hans@owltronix.com wrote:
> From: Hans Holmberg <hans.holmberg@cnexlabs.com>
>
> pblk_line_meta_free might sleep (it can end up calling vfree, depending
> on how we allocate lba lists), and this can lead to a BUG()
> if we wake up on a different cpu and release the lock.
>
> As there is no point of grabbing the free lock when pblk has shut down,
> remove the lock.
>
> Signed-off-by: Hans Holmberg <hans.holmberg@cnexlabs.com>
> ---
> drivers/lightnvm/pblk-init.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/lightnvm/pblk-init.c b/drivers/lightnvm/pblk-init.c
> index f9a3e47b6a93..eb0135c77805 100644
> --- a/drivers/lightnvm/pblk-init.c
> +++ b/drivers/lightnvm/pblk-init.c
> @@ -584,14 +584,12 @@ static void pblk_lines_free(struct pblk *pblk)
> struct pblk_line *line;
> int i;
>
> - spin_lock(&l_mg->free_lock);
> for (i = 0; i < l_mg->nr_lines; i++) {
> line = &pblk->lines[i];
>
> pblk_line_free(line);
> pblk_line_meta_free(l_mg, line);
> }
> - spin_unlock(&l_mg->free_lock);
>
> pblk_line_mg_free(pblk);
>
>
Thanks Hans. Applied for 5.1.
next prev parent reply other threads:[~2019-01-22 19:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 10:15 hans
2019-01-22 19:48 ` Matias Bjørling [this message]
2019-01-24 13:19 ` Javier González
2019-01-25 9:15 ` Hans Holmberg
2019-01-25 9:37 ` Javier González
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a0bceb9f-4f8a-1b69-8ef3-f2bc0747a3b5@lightnvm.io \
--to=mb@lightnvm.io \
--cc=hans.holmberg@cnexlabs.com \
--cc=hans@owltronix.com \
--cc=javier@javigon.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®