Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1590925 > unrolled thread

Re: [GIT PULL] vfs patches for 4.11

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [GIT PULL] vfs patches for 4.11 Amir Goldstein <amir73il@gmail.com> - 2017-03-02 09:50 +0100
    Re: [GIT PULL] vfs patches for 4.11 Al Viro <viro@ZenIV.linux.org.uk> - 2017-03-02 11:00 +0100
      Re: [GIT PULL] vfs patches for 4.11 Amir Goldstein <amir73il@gmail.com> - 2017-03-03 09:30 +0100

#1590925 — Re: [GIT PULL] vfs patches for 4.11

On Mon, Feb 20, 2017 at 7:17 PM, Al Viro <viro@zeniv.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.

[toc] | [next] | [standalone]

#1590951

On Thu, Mar 02, 2017 at 10:32:08AM +0200, Amir Goldstein wrote:
> On Mon, Feb 20, 2017 at 7:17 PM, Al Viro <viro@zeniv.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?

Yes.  As the matter of fact, it will be one of the pull requests in today's
pile.

[toc] | [prev] | [next] | [standalone]

#1591741

On Thu, Mar 2, 2017 at 11:57 AM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> On Thu, Mar 02, 2017 at 10:32:08AM +0200, Amir Goldstein wrote:
>> On Mon, Feb 20, 2017 at 7:17 PM, Al Viro <viro@zeniv.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?
>
> Yes.  As the matter of fact, it will be one of the pull requests in today's
> pile.

Cool.

Miklos,

This vfs pile was already pulled.
Could you please follow up with overlayfs 4.11 pull request.

I also verified that overlayfs-next and rebased-statx have no conflicts
(copy_up.c is correctly auto-merged)
and re-tested concurrent copy up and -g overlay/quick with the test merge.

Thanks,
Amir.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web