On Fri, Apr 20, 2018 at 11:29:45AM -0700, Andrew Morton wrote: > On Fri, 20 Apr 2018 16:58:46 +0100 Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > > > Assorted fixes. Some of that is only a matter with fault injection > > (broken handling of small allocation failure in various mount-related places), > > but the last one is a root-triggerable stack overflow, and combined with > > userns it gets really nasty ;-/ > > > > The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338: > > > > Linux 4.17-rc1 (2018-04-15 18:24:20 -0700) > > > > are available in the git repository at: > > > > git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus > > > > for you to fetch changes up to 16a34adb9392b2fe4195267475ab5b472e55292c: > > > > Don't leak MNT_INTERNAL away from internal mounts (2018-04-19 23:52:15 -0400) > > ... > > > > Tetsuo Handa (1): > > mm,vmscan: Allow preallocating memory for register_shrinker(). > > Confused. You had a bunch of issues with this patch > (http://lkml.kernel.org/r/20180411005938.GN30522@xxxxxxxxxxxxxxxxxx) > and Tetsuo sent out a v2 but now we've merged the v1. Deliberate? I think by that time I'd applied v1 and fixed those issues myself (same as his variant, modulo slightly different names). > Also, it would be nice if you could get the Link: thing working in your > commits please - this one took a bit of hunting down. *blink* What Link: thing? You mean lkml.kernel.org references to original postings? Or is it something else? Never done that, actually; any tips re tools needed for that? Normally it's save a bunch of postings into a local file in mutt, scp it over to development box, then git am -s - either all at once, or step by step with ediiting and git commit --amend in between... I realize that message-id can be picked and massaged into Link: ... form, of course, but I'd rather not reinvent the wheel if it's already done by somebody...
