On Thu, Oct 22, 2015 at 12:41 AM, Vito Caputo <vito.caputo@xxxxxxxxxx> wrote: > Greetings, > > We've been receiving reports of ooms triggered by the high-order allocation > in the overlayfs ovl_copy_xattr() implementation. > > The bug is in the handling of direct-reclaim high-order allocations (and > appears to be known and actively being worked on). Rather than do something > hacky in mm and potentially destabilize everything for a quick fix, I've put > together a simple patch changing the allocation to an as-needed krealloc() > approach which should eliminate the ooms, since 64KiB extended attributes > are uncommon. Thanks. Pushed to git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
