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]

Message-Id: <1250289913.5085.17.camel@pc1117.cambridge.arm.com>
Date:	Fri, 14 Aug 2009 23:45:13 +0100
From:	Catalin Marinas <catalin.marinas@....com>
To:	Ingo Molnar <mingo@...e.hu>
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()

Hi Ingo,

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

I updated the original patch for cond_resched() slightly (to check for
objects they may be annotated during a scan_block loop). I also added a
patch with an annotation for the memory hole at 0x20000000 on your
x86_64 platform. I don't have such hardware to be able to check, so I
would be grateful if you can acknowledge them.

I'll post the patches as replies to this e-mail.

Thanks.

-- 
Catalin

--
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/