From: "Miles Lane" <miles.lane@gmail.com>
To: "Tejun Heo" <htejun@gmail.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22-rc6-mm1 -- BUG - EIP: [<c01a77a1>] sysfs_addrm_finish+0x1c2/0x226 SS:ESP 0068:c5ff9db8
Date: Sat, 7 Jul 2007 21:56:06 -0700 [thread overview]
Message-ID: <a44ae5cd0707072156y7d0c9e5am2ded3efdc036bcf7@mail.gmail.com> (raw)
In-Reply-To: <469038EF.7040709@gmail.com>
On 7/7/07, Tejun Heo <htejun@gmail.com> wrote:
> Miles Lane wrote:
> >> Weird, that's unrelated path. It seems sd->s_parent is NULL in
> >> sysfs_link_sibling(), which doesn't make sense because it's being called
> >> from sysfs_create_link() which makes sure parent_sd isn't NULL &&
> >> sysfs_addrm_start() should have caused oops earlier as it deferences
> >> parent_sd.
> >>
> >> Can you please retry the test (test clean 2.6.22-rc6-mm1, apply patch,
> >> rebuild and test)?
> >
> > I downloaded linux-2.6.22-rc6.tar.bz2, applied 2.6.22-rc6-mm1 and then
> > applied your second patch. I still get the same OOPS I reported to you
> > and Andrew in the image I attached to my previous message.
>
> Thanks a lot. Just in case, if you remove the patch (patch -R -p1), the
> oops goes away, right?
I double-checked. I can boot fine after building without your patch.
Also, I reproduced the initial BUG I reported (triggered by
"modprobe -r ipw2200").
Miles
next prev parent reply other threads:[~2007-07-08 4:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 16:32 Miles Lane
2007-07-03 16:49 ` Andrew Morton
2007-07-04 6:23 ` Tejun Heo
2007-07-04 7:36 ` Miles Lane
2007-07-05 7:32 ` Tejun Heo
[not found] ` <a44ae5cd0707060101g38147b2gb3d33d9903082113@mail.gmail.com>
2007-07-07 6:47 ` Tejun Heo
2007-07-08 0:53 ` Miles Lane
2007-07-08 1:07 ` Tejun Heo
2007-07-08 4:56 ` Miles Lane [this message]
2007-07-11 7:21 ` Tejun Heo
2007-07-11 9:48 ` Tejun Heo
2007-07-11 22:39 ` Miles Lane
2007-07-12 3:04 ` Tejun Heo
2007-07-12 8:25 ` Miles Lane
2007-07-13 8:35 ` Tejun Heo
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=a44ae5cd0707072156y7d0c9e5am2ded3efdc036bcf7@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®