From: Marcin Jurkowski <marcin1j@gmail.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Sven Geggus <lists@fuchsschwanzdomain.de>, linux-kernel@vger.kernel.org
Subject: Re: Re: reproducible w1 oops on recent kernels (at least since 3.2.x)
Date: Sat, 2 Mar 2013 01:11:03 +0100 [thread overview]
Message-ID: <20130302001103.GB18026@gmail.com> (raw)
In-Reply-To: <20130116141627.GA23638@ioremap.net>
On Wednesday, January 16, 2013 3:16:38 PM UTC+1, Evgeniy Polyakov wrote:
> Can you confirm that bug still persists and that it doesn't exist in
>
> 3.1? Do you have a possibility to bisect w1 bits down to broken
> commit?
Hi
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.
Regards
next prev parent reply other threads:[~2013-03-02 0:11 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 [this message]
2013-03-02 9:45 ` Sven Geggus
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=20130302001103.GB18026@gmail.com \
--to=marcin1j@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@fuchsschwanzdomain.de \
--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