Commit 291ad9a7 authored by Alessandro Rubini's avatar Alessandro Rubini

FMC: fix locking in sample chardev driver

The fmc-chardev module was over-locking, by calling misc
register/unregister while holding its spinlock.  This reported a
"scheduling while atomic" error.

Since the misc driver already serializes operations internally, this
commit downgrades the fmc-chardev lock to just cover its own list.
Reported-by: 's avatarSasha Levin <sasha.levin@oracle.com>
Reported-by: 's avatarFengguang Wu <fengguang.wu@intel.com>
Signed-off-by: Alessandro Rubini's avatarAlessandro Rubini <rubini@gnudd.com>
Signed-off-by: 's avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
parent 766edad3
...@@ -142,18 +142,17 @@ static int fc_probe(struct fmc_device *fmc) ...@@ -142,18 +142,17 @@ static int fc_probe(struct fmc_device *fmc)
fc->misc.fops = &fc_fops; fc->misc.fops = &fc_fops;
fc->misc.name = kstrdup(dev_name(&fmc->dev), GFP_KERNEL); fc->misc.name = kstrdup(dev_name(&fmc->dev), GFP_KERNEL);
spin_lock(&fc_lock);
ret = misc_register(&fc->misc); ret = misc_register(&fc->misc);
if (ret < 0) if (ret < 0)
goto err_unlock; goto out;
spin_lock(&fc_lock);
list_add(&fc->list, &fc_devices); list_add(&fc->list, &fc_devices);
spin_unlock(&fc_lock); spin_unlock(&fc_lock);
dev_info(&fc->fmc->dev, "Created misc device \"%s\"\n", dev_info(&fc->fmc->dev, "Created misc device \"%s\"\n",
fc->misc.name); fc->misc.name);
return 0; return 0;
err_unlock: out:
spin_unlock(&fc_lock);
kfree(fc->misc.name); kfree(fc->misc.name);
kfree(fc); kfree(fc);
return ret; return ret;
...@@ -173,10 +172,10 @@ static int fc_remove(struct fmc_device *fmc) ...@@ -173,10 +172,10 @@ static int fc_remove(struct fmc_device *fmc)
spin_lock(&fc_lock); spin_lock(&fc_lock);
list_del(&fc->list); list_del(&fc->list);
spin_unlock(&fc_lock);
misc_deregister(&fc->misc); misc_deregister(&fc->misc);
kfree(fc->misc.name); kfree(fc->misc.name);
kfree(fc); kfree(fc);
spin_unlock(&fc_lock);
return 0; return 0;
} }
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment