[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOQ4uxjE0COiGABRwA1Zz-kOAwYjUfGdJitT8AhgHBU2r8sBpA@mail.gmail.com>
Date: Thu, 2 Mar 2017 10:32:08 +0200
From: Amir Goldstein <amir73il@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>,
Miklos Szeredi <miklos@...redi.hu>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [GIT PULL] vfs patches for 4.11
On Mon, Feb 20, 2017 at 7:17 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
> On Mon, Feb 20, 2017 at 05:19:00PM +0100, Miklos Szeredi wrote:
>> Hi Al,
>>
>> Please pull from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git for-viro
>>
>> Amir Goldstein (4):
>> vfs: create vfs helper vfs_tmpfile()
>> vfs: deny fallocate() on directory
>> vfs: deny copy_file_range() for non regular files
>> vfs: wrap write f_ops with file_{start,end}_write()
>
> The last one could have a better summary, but anyway - pulled.
Al,
Please excuse my impatience, but do you plan to send these out to
Linus for 4.11?
If not, Miklos, could possibly ask Linus to pull overlayfs-next, which have been
soaking in linux-next for a while now.
overlayfs-next contains only my 4 VFS patches above, which are not that
controversial IMO.
It'd be nice to get rid of the "big copy up lock" for 4.11.
Thanks,
Amir.
Powered by blists - more mailing lists