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
| ||
|
Date: Sun, 12 Aug 2007 13:48:31 +0800 From: WU Fengguang <wfg@...l.ustc.edu.cn> To: Balbir Singh <balbir@...ux.vnet.ibm.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: [BUGFIX] NULL pointer dereference in __vm_enough_memory() On Sat, Aug 11, 2007 at 11:31:09PM +0530, Balbir Singh wrote: > Andrew Morton wrote: > > On Sat, 11 Aug 2007 20:00:12 +0530 "Balbir Singh" <balbir@...ux.vnet.ibm.com> wrote: > >>> > >> Shouldn't we just not stop vm accounting for kernel threads? > >> > > > > Could be. It'd help heaps if we knew which patch in -mm caused > > this, but from a quick peek it seems to me that mainline should be > > vulnerable as well. > > Thats a valid point. It would be interesting to see what the overcommit > setting was, when the panic occurred. FYI, I do have nondefault overcommit settings: vm.overcommit_memory = 2 vm.lowmem_reserve_ratio = 1 1 - 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