public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Matias Bjørling" <mb@lightnvm.io>
To: Wenwei Tao <ww.tao0320@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] lightnvm: missing nvm_lock acquire
Date: Wed, 25 Nov 2015 12:37:00 +0100	[thread overview]
Message-ID: <56559D5C.6090004@lightnvm.io> (raw)
In-Reply-To: <CACygaLCubz-+ScTrZhXUn9qKobdi4QaQ3Y0VSMQKndgG2QPvyQ@mail.gmail.com>

On 11/25/2015 09:57 AM, Wenwei Tao wrote:
> Hi Matias
> I think list_for_each_entry_safe(pos, n, head, member) cannot avoid
> race condition
> the item point by ‘n’ can be deleted and freed in the same time we
> operate on 'pos'
> so lock is still necessary.
>
I've made the patch like this, ok?

To avoid race conditions, traverse dev, media manager,
and target lists and also register, unregister entries
to/from them, should be always under the nvm_lock control.

Signed-off-by: Wenwei Tao <ww.tao0320@gmail.com>
Signed-off-by: Matias Bjørling <m@bjorling.me>
---
  drivers/lightnvm/core.c | 5 ++++-
  1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/lightnvm/core.c b/drivers/lightnvm/core.c
index ea6dba5..9f901f6 100644
--- a/drivers/lightnvm/core.c
+++ b/drivers/lightnvm/core.c
@@ -127,9 +127,11 @@ static struct nvm_dev *nvm_find_nvm_dev(const char 
*name)
  {
  	struct nvm_dev *dev;

+	down_write(&nvm_lock);
  	list_for_each_entry(dev, &nvm_devices, devices)
  		if (!strcmp(name, dev->name))
  			return dev;
+	up_write(&nvm_lock);

  	return NULL;
  }
@@ -388,13 +390,14 @@ static int nvm_create_target(struct nvm_dev *dev,
  		}
  	}

+	down_write(&nvm_lock);
  	tt = nvm_find_target_type(create->tgttype);
  	if (!tt) {
  		pr_err("nvm: target type %s not found\n", create->tgttype);
+		up_write(&nvm_lock);
  		return -EINVAL;
  	}

-	down_write(&nvm_lock);
  	list_for_each_entry(t, &dev->online_targets, list) {
  		if (!strcmp(create->tgtname, t->disk->disk_name)) {
  			pr_err("nvm: target name already exists.\n");
-- 
2.1.4



  parent reply	other threads:[~2015-11-25 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 15:24 [PATCH] lightnvm: missing nvm_lock acquire Wenwei Tao
2015-11-24 15:35 ` kbuild test robot
2015-11-24 18:36 ` Matias
2015-11-25  8:57   ` Wenwei Tao
2015-11-25 11:24     ` Matias Bjørling
2015-11-25 11:37     ` Matias Bjørling [this message]
2015-11-25 13:11       ` Wenwei Tao
2015-11-25 14:18         ` Wenwei Tao
2015-11-25 14:27           ` Matias Bjørling

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=56559D5C.6090004@lightnvm.io \
    --to=mb@lightnvm.io \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ww.tao0320@gmail.com \
    /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