From: Tejun Heo <htejun@gmail.com>
To: Miles Lane <miles.lane@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: Sun, 08 Jul 2007 10:07:59 +0900 [thread overview]
Message-ID: <469038EF.7040709@gmail.com> (raw)
In-Reply-To: <a44ae5cd0707071753g6dd4445bsaac2e2296327e510@mail.gmail.com>
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?
--
tejun
next prev parent reply other threads:[~2007-07-08 1:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 16:32 2.6.22-rc6-mm1 -- BUG - EIP: [<c01a77a1>] sysfs_addrm_finish+0x1c2/0x226 SS:ESP 0068:c5ff9db8 Miles Lane
2007-07-03 16:49 ` Andrew Morton
2007-07-03 16:49 ` Andrew Morton
2007-07-04 6:23 ` Tejun Heo
2007-07-04 6:23 ` Tejun Heo
2007-07-04 7:36 ` Miles Lane
2007-07-05 7:32 ` Tejun Heo
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 [this message]
2007-07-08 4:56 ` Miles Lane
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=469038EF.7040709@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.