From: ebiederm@xmission.com (Eric W. Biederman)
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Holger Schurig <hs4233@mail.mn-solutions.de>,
linux-kernel@vger.kernel.org
Subject: Re: OOPS in sysctl.c
Date: Wed, 06 Feb 2008 17:51:43 -0700 [thread overview]
Message-ID: <m1myqdd1wg.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20080206190353.GB1732@martell.zuzino.mipt.ru> (Alexey Dobriyan's message of "Wed, 6 Feb 2008 22:03:53 +0300")
Alexey Dobriyan <adobriyan@gmail.com> writes:
> On Wed, Feb 06, 2008 at 12:24:20AM -0800, Andrew Morton wrote:
>> On Tue, 5 Feb 2008 12:24:56 +0100 Holger Schurig <hs4233@mail.mn-solutions.de>
> wrote:
>>
>> > > I have an embedded target (PXA255 based) where I have a nice
>> > > running kernel 2.6.15. Today I'm trying to get 2.6.24 running
>> > > on it.
>> >
>>
>> Backtrace:
>> [<c0038bbc>] (sysctl_head_next+0x0/0x64) from [<c00a4b80>]
> (proc_sys_readdir+0x360/0x394)
>> r4:00000000
>> [<c00a4820>] (proc_sys_readdir+0x0/0x394) from [<c007c860>]
> (vfs_readdir+0x70/0x98)
>> [<c007c7f0>] (vfs_readdir+0x0/0x98) from [<c007cdf0>]
> (sys_getdents64+0x6c/0xc0)
>> [<c007cd84>] (sys_getdents64+0x0/0xc0) from [<c0023e60>]
> (ret_fast_syscall+0x0/0x2c)
>
> Please, post .config and "ls -lR /proc/sys" output _before_ suspend/resume.
Just to keep this on track. It sounds like his suspend/resume backport was
incomplete and something there is smashing the list sysctl_head_next follows.
This would both cause files to disappear, and an oops.
Possibly it isn't an incomplete backport but instead a memory smash that hits
different places in different kernels.
Eric
next prev parent reply other threads:[~2008-02-07 0:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:45 Holger Schurig
2008-02-05 11:24 ` Holger Schurig
2008-02-06 8:24 ` Andrew Morton
2008-02-06 19:03 ` Alexey Dobriyan
2008-02-07 0:51 ` Eric W. Biederman [this message]
2008-02-07 10:46 ` Holger Schurig
2008-02-07 10:46 ` Holger Schurig
2008-02-07 11:02 ` Holger Schurig
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=m1myqdd1wg.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hs4233@mail.mn-solutions.de \
--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®