| 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
| ||
|
Message-ID: <20110318194135.GA4746@prasad-kvm> Date: Fri, 18 Mar 2011 19:41:35 +0000 From: Prasad Joshi <prasadjoshi124@...il.com> To: akpm@...ux-foundation.org, linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org, prasadjoshi124@...il.com, mitra@...nfotech.com Cc: chris@...kel.net, x86@...nel.org, jdike@...toit.com, tj@...nel.org, cmetcalf@...era.com, linux-sh@...r.kernel.org, liqin.chen@...plusct.com, lennox.wu@...il.com, schwidefsky@...ibm.com, heiko.carstens@...ibm.com, linux390@...ibm.com, benh@...nel.crashing.org, paulus@...ba.org, linuxppc-dev@...ts.ozlabs.org, kyle@...artin.ca, deller@....de, jejb@...isc-linux.org, linux-parisc@...r.kernel.org, dhowells@...hat.com, yasutake.koichi@...panasonic.com, linux-am33-list@...hat.com, ralf@...ux-mips.org, linux-mips@...ux-mips.org, monstr@...str.eu, microblaze-uclinux@...e.uq.edu.au, geert@...ux-m68k.org, zippel@...ux-m68k.org, sammy@...my.net, linux-m68k@...ts.linux-m68k.org, takata@...ux-m32r.org, linux-m32r@...linux-m32r.org, tony.luck@...el.com, fenghua.yu@...el.com, linux-ia64@...r.kernel.org, starvik@...s.com, jesper.nilsson@...s.com, linux-cris-kernel@...s.com, hans-christian.egtvedt@...el.com, linux@....linux.org.uk, rth@...ddle.net, linux-alpha@...r.kernel.org Subject: [RFC][PATCH v3 00/22] __vmalloc: Propagating GFP allocation flag inside __vmalloc() A filesystem might run into a problem while calling __vmalloc(GFP_NOFS) inside a lock. It is expected than __vmalloc when called with GFP_NOFS should not callback the filesystem code even incase of the increased memory pressure. But the problem is that even if we pass this flag, __vmalloc itself allocates memory with GFP_KERNEL. Using GFP_KERNEL allocations may go into the memory reclaim path and try to free memory by calling file system evict_inode function. Which might lead into deadlock. For further details http://marc.info/?l=linux-mm&m=128942194520631&w=4 https://bugzilla.kernel.org/show_bug.cgi?id=30702 The patch passes the gfp allocation flag all the way down to those allocating functions. arch/arm/include/asm/pgalloc.h | 11 +++++- arch/avr32/include/asm/pgalloc.h | 8 ++++- arch/cris/include/asm/pgalloc.h | 10 ++++- arch/frv/include/asm/pgalloc.h | 3 ++ arch/frv/include/asm/pgtable.h | 1 + arch/frv/mm/pgalloc.c | 9 ++++- arch/ia64/include/asm/pgalloc.h | 24 +++++++++++-- arch/m32r/include/asm/pgalloc.h | 11 ++++-- arch/m68k/include/asm/motorola_pgalloc.h | 20 +++++++++-- arch/m68k/include/asm/sun3_pgalloc.h | 14 ++++++-- arch/m68k/mm/memory.c | 9 ++++- arch/microblaze/include/asm/pgalloc.h | 3 ++ arch/microblaze/mm/pgtable.c | 13 +++++-- arch/mips/include/asm/pgalloc.h | 22 ++++++++---- arch/mn10300/include/asm/pgalloc.h | 2 + arch/mn10300/mm/pgtable.c | 10 ++++- arch/parisc/include/asm/pgalloc.h | 21 ++++++++--- arch/powerpc/include/asm/pgalloc-32.h | 2 + arch/powerpc/include/asm/pgalloc-64.h | 27 +++++++++++--- arch/powerpc/mm/pgtable_32.c | 10 ++++- arch/s390/include/asm/pgalloc.h | 30 +++++++++++++--- arch/s390/mm/pgtable.c | 22 +++++++++--- arch/score/include/asm/pgalloc.h | 13 ++++--- arch/sh/include/asm/pgalloc.h | 8 ++++- arch/sh/mm/pgtable.c | 8 ++++- arch/sparc/include/asm/pgalloc_32.h | 5 +++ arch/sparc/include/asm/pgalloc_64.h | 17 ++++++++- arch/tile/include/asm/pgalloc.h | 13 ++++++- arch/tile/mm/pgtable.c | 10 ++++- arch/um/include/asm/pgalloc.h | 1 + arch/um/kernel/mem.c | 21 ++++++++--- arch/x86/include/asm/pgalloc.h | 17 ++++++++- arch/x86/mm/pgtable.c | 8 ++++- arch/xtensa/include/asm/pgalloc.h | 9 ++++- arch/xtensa/mm/pgtable.c | 11 +++++- include/asm-generic/4level-fixup.h | 8 +++- include/asm-generic/pgtable-nopmd.h | 3 +- include/asm-generic/pgtable-nopud.h | 1 + include/linux/mm.h | 40 ++++++++++++++++----- mm/memory.c | 14 ++++--- mm/vmalloc.c | 57 ++++++++++++++++++++---------- 41 files changed, 427 insertions(+), 119 deletions(-) -- 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