linux-kernel - Re: bug in lmb_enforce_memory

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: <20080815.195724.238982506.davem@davemloft.net>
Date:	Fri, 15 Aug 2008 19:57:24 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	michael@...erman.id.au
Cc:	linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org
Subject: Re: bug in lmb_enforce_memory_limit()

From: Michael Ellerman <michael@...erman.id.au>
Date: Sat, 16 Aug 2008 10:46:22 +1000

> On Fri, 2008-08-15 at 15:25 -0700, David Miller wrote:
> > Sounds great.  Mind if I push the following to Linus?
> 
> Looks good to me.
> 
> I'll test it on Monday. I don't know if I have a system with memory
> holes to test on, but I take it you do?
> 
> I notice some of our 32-bit code is using lmb_enforce_memory_limit() to
> enforce an address limit, which is technically broken, but is probably
> fine because it doesn't need to worry about holes.

Sounds like fun :-)

> Acked-by: Michael Ellerman <michael@...erman.id.au>

Thanks for reviewing Michael.
--
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/