[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTinOQ1yXqJJVo=k9YSM=xG2Fg2GSAE8z2O3dGsME@mail.gmail.com>
Date: Tue, 29 Mar 2011 12:19:01 +0800
From: Américo Wang <xiyou.wangcong@...il.com>
To: Dave Jones <davej@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: vma corruption in today's -git
On Tue, Mar 29, 2011 at 12:09 PM, Dave Jones <davej@...hat.com> wrote:
> Running a kernel that I built from a git pull from this afternoon,
> I ran a barrage of stress tests, including some of the new syscall fuzzing
> work that I've been working on. Everything seemed just fine, except that
> after I had stopped running everything, loadavg was still at 6, with
> top showing kworker processes running at high % of cpu.
>
> I ran perf top, and got this ..
>
> BUG: unable to handle kernel paging request at fffffffffffffff3
> IP: [<ffffffff8118d3e9>] vma_stop.clone.3+0x18/0x33
Should be fixed by:
commit 76597cd31470fa130784c78fadb4dab2e624a723
Author: Linus Torvalds <torvalds@...ux-foundation.org>
Date: Sun Mar 27 19:09:29 2011 -0700
proc: fix oops on invalid /proc/<pid>/maps access
When m_start returns an error, the seq_file logic will still call m_stop
with that error entry, so we'd better make sure that we check it before
using it as a vma.
Introduced by commit ec6fd8a4355c ("report errors in /proc/*/*map*
sanely"), which replaced NULL with various ERR_PTR() cases.
(On ia64, you happen to get a unaligned fault instead of a page fault,
since the address used is generally some random error code like -EPERM)
Reported-by: Anca Emanuel <anca.emanuel@...il.com>
Reported-by: Tony Luck <tony.luck@...el.com>
Cc: Al Viro <viro@...iv.linux.org.uk>
Cc: Américo Wang <xiyou.wangcong@...il.com>
Cc: Stephen Wilson <wilsons@...rt.ca>
Signed-off-by: Linus Torvalds <torvalds@...ux-foundation.org>
--
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/
Powered by blists - more mailing lists