aboutsummaryrefslogtreecommitdiff
path: root/init
diff options
context:
space:
mode:
authorMarcin Jurkowski <marcin1j@gmail.com>2013-03-02 14:50:15 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-03-12 16:20:46 -0700
commit9d1817cab2f030f6af360e961cc69bb1da8ad765 (patch)
tree5061bd02d140075839e0b71180a594d869c40f7a /init
parent34ccd8738e34180af34544d2bdd053e60e44a224 (diff)
w1: fix oops when w1_search is called from netlink connector
On Sat, Mar 02, 2013 at 10:45:10AM +0100, Sven Geggus wrote: > This is the bad commit I found doing git bisect: > 04f482faf50535229a5a5c8d629cf963899f857c is the first bad commit > commit 04f482faf50535229a5a5c8d629cf963899f857c > Author: Patrick McHardy <kaber@trash.net> > Date: Mon Mar 28 08:39:36 2011 +0000 Good job. I was too lazy to bisect for bad commit;) Reading the code I found problematic kthread_should_stop call from netlink connector which causes the oops. After applying a patch, I've been testing owfs+w1 setup for nearly two days and it seems to work very reliable (no hangs, no memleaks etc). More detailed description and possible fix is given below: Function w1_search can be called from either kthread or netlink callback. While the former works fine, the latter causes oops due to kthread_should_stop invocation. This patch adds a check if w1_search is serving netlink command, skipping kthread_should_stop invocation if so. Signed-off-by: Marcin Jurkowski <marcin1j@gmail.com> Acked-by: Evgeniy Polyakov <zbr@ioremap.net> Cc: Josh Boyer <jwboyer@gmail.com> Tested-by: Sven Geggus <lists@fuchsschwanzdomain.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: stable <stable@vger.kernel.org> # 3.0+
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions