linux-kernel - Re: kmemleak: Protect the seq start/next/stop sequence byrcu_read

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, 13 Aug 2009 08:52:53 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: kmemleak: Protect the seq start/next/stop sequence
	byrcu_read_lock()


* Catalin Marinas <catalin.marinas@....com> wrote:

> On Wed, 2009-08-12 at 21:52 +0100, Ingo Molnar wrote:
> > * Catalin Marinas <catalin.marinas@....com> wrote:
> > 
> > > kmemleak: Allow rescheduling during an object scanning
> > 
> > i tried this in -tip testing, and it crashes quickly:
> > 
> > [   81.900051] BUG: unable to handle kernel paging request at ffff880020000000
> > [   81.901382] IP: [<ffffffff8112ae7e>] scan_block+0xee/0x190
> 
> It looks like my check for object->flags & OBJECT_ALLOCATED in 
> scan_object() may not be enough.
> 
> I'm a bit confused as the config you sent says x86_32 but the 
> fault address above looks like a 64 bit one (and my knowledge of 
> x86 isn't great). Is this x86_64?

ahm indeed. It crashed not straight during bootup but while my tests 
built the next kernel iteration already (with a new random config), 
so i sent the config of the next kernel.

I've attached the right config.

	Ingo

View attachment "config" of type "text/plain" (68322 bytes)