From: Sven Geggus <lists@fuchsschwanzdomain.de>
To: Marcin Jurkowski <marcin1j@gmail.com>
Cc: Evgeniy Polyakov <zbr@ioremap.net>, linux-kernel@vger.kernel.org
Subject: Re: reproducible w1 oops on recent kernels (at least since 3.2.x)
Date: Sat, 2 Mar 2013 10:45:10 +0100 [thread overview]
Message-ID: <20130302094510.GA4695@geggus.net> (raw)
In-Reply-To: <20130302001103.GB18026@gmail.com>
Marcin Jurkowski schrieb am Samstag, den 02. März um 01:11 Uhr:
> I can confirm that this bug persists in recent kernel. Onewire netlink
> interface to W1_SEARCH command must have been broken for a while.
>
> Good news is that it seems to be easy to fix. I'll post an explanation
> and a patch tomorrow.
I did not send this to the kernel Mailinglist but to Evgeniy
only. 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
connector: convert to synchronous netlink message processing
Commits 01a16b21 (netlink: kill eff_cap from structnetlink_skb_parms)
and c53fa1ed (netlink: kill loginuid/sessionid/sid members fromstruct
netlink_skb_parms) removed some members from structnetlink_skb_parms
that depend on the current context, all netlink users are nowrequired
to do synchronous message processing.
connector however queues received messages and processes them ina work
queue, which is not valid anymore. This patch converts connectorto do
synchronous message processing by invoking the registeredcallback
handler directly from the netlink receive function.
In order to avoid invoking the callback with connector locksheld, a
reference count is added to struct cn_callback_entry, thereference
is taken when finding a matching callback entry on the device'squeue_list
and released after the callback handler has been invoked.
Signed-off-by: Patrick McHardy <kaber@trash.net>
Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
Sven
--
"C Is Quirky, Flawed, And An Enormous Success."
(Dennis M. Ritchie)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web
next prev parent reply other threads:[~2013-03-02 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 18:44 reproducible w1 oops on recent kernels (at least since 3.2.x) Sven Geggus
2013-01-16 14:16 ` Evgeniy Polyakov
2013-03-02 0:11 ` Marcin Jurkowski
2013-03-02 9:45 ` Sven Geggus [this message]
2013-03-02 13:50 ` [PATCH 1/1] w1: fix oops when w1_search is called from netlink connector Marcin Jurkowski
2013-03-03 15:36 ` Sven Geggus
2013-03-03 20:54 ` Evgeniy Polyakov
2013-03-03 22:41 ` GregKH
2013-03-11 13:18 ` Josh Boyer
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=20130302094510.GA4695@geggus.net \
--to=lists@fuchsschwanzdomain.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin1j@gmail.com \
--cc=zbr@ioremap.net \
/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