Messages in this thread | | | Date | Tue, 22 Jul 2014 18:47:00 +0200 | Subject | Re: VFS tree for 3.17? | From | Richard Weinberger <> |
| |
On Tue, Jul 22, 2014 at 6:24 PM, Christoph Hellwig <hch@infradead.org> wrote: > On Wed, Jul 16, 2014 at 04:41:36AM -0700, Christoph Hellwig wrote: >> Hi Al, >> >> Do you plan to put a VFS tree together for 3.17? To me the various >> renameat2 bits from Miklos are something I'd really prefer to not miss, >> but there might be other bits waiting for attention as well. > > Another weeks has passed and I'd really like to make sure we don't > let the VFS leap. > > I'll try to put together a tree over the next days so we can at least > get a minium amount of linux-next exposure. Candidates are: > > - the direct-io.c warning fix from Boaz (really should 3.16 actually) > - the unmount on symlink reference count fix
This fix is also stable material. The issue as introduced in 3.12 by 8033426e6b (vfs: allow umount to handle mountpoints without revalidating them)
> - the rename/rename2 patches from Mikilos. These are a bit older > and could use a respin. > > Anything else I've missed? > > -- > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html
-- Thanks, //richard
| |