linux-kernel - Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem")

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 20 Dec 2007 07:54:48 -0500
From:	"Miles Lane" <miles.lane@...il.com>
To:	"David Howells" <dhowells@...hat.com>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Ingo Molnar" <mingo@...hat.com>,
	"Russell King" <rmk+lkml@....linux.org.uk>
Subject: Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem")

On Dec 20, 2007 6:37 AM, David Howells <dhowells@...hat.com> wrote:
> Andrew Morton <akpm@...ux-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.

I tested the patch Andrew sent.  I ran "cat /proc/iomem" before trying
a suspend-to-disk.  It worked fine.  Then I suspended and resumed.
This time, "cat /proc/iomem" caused the stack trace to be generated.
So, you are right, you patch is not the problem.

Thanks,
              Miles
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/