From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem")
Date: Thu, 20 Dec 2007 11:37:20 +0000 [thread overview]
Message-ID: <5102.1198150640@redhat.com> (raw)
In-Reply-To: <20071219220307.d69c0fde.akpm@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> wrote:
> I would be suspecting iget-stop-procfs-from-using-iget-and-read_inode.patch.
I think your suspicions are very unlikely. The patch only affects
proc_get_inode() - and looking at the patch backtrace, it looks like the
system is successfully past that already (it's unlikely that
proc_reg_read+0x60/0x74 would have been reached otherwise).
If my patch to procfs is wrong, it would affect all proc files and ought be
immediately detectable.
David
next prev parent reply other threads:[~2007-12-20 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 4:40 OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 Miles Lane
2007-12-20 4:48 ` OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem") Miles Lane
2007-12-20 5:35 ` Miles Lane
2007-12-20 6:03 ` Andrew Morton
2007-12-20 10:53 ` Alexey Dobriyan
2007-12-20 11:37 ` David Howells [this message]
2007-12-20 12:54 ` Miles Lane
2007-12-20 9:10 ` Russell King
2007-12-20 13:38 ` OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem" AFTER suspend-to-disk/resume) Miles Lane
2007-12-20 17:32 ` Andrew Morton
[not found] ` <a44ae5cd0712202158u31c8b4e1lf5b0df89dde20e7e@mail.gmail.com>
2007-12-21 6:18 ` Miles Lane
2007-12-21 6:29 ` Andrew Morton
2007-12-21 16:06 ` Miles Lane
2007-12-21 20:00 ` Andrew Morton
2007-12-21 21:18 ` Miles Lane
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=5102.1198150640@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=mingo@redhat.com \
--cc=rmk+lkml@arm.linux.org.uk \
/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