[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.02.2009281105200.27411@file01.intranet.prod.int.rdu2.redhat.com>
Date: Mon, 28 Sep 2020 11:22:28 -0400 (EDT)
From: Mikulas Patocka <mpatocka@...hat.com>
To: Matthew Wilcox <willy@...radead.org>
cc: Dave Chinner <david@...morbit.com>,
Dan Williams <dan.j.williams@...el.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Vishal Verma <vishal.l.verma@...el.com>,
Dave Jiang <dave.jiang@...el.com>,
Ira Weiny <ira.weiny@...el.com>, Jan Kara <jack@...e.cz>,
Eric Sandeen <esandeen@...hat.com>,
Dave Chinner <dchinner@...hat.com>,
"Kani, Toshi" <toshi.kani@....com>,
"Norton, Scott J" <scott.norton@....com>,
"Tadakamadla, Rajesh (DCIG/CDI/HPS Perf)"
<rajesh.tadakamadla@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>
Subject: Re: NVFS XFS metadata (was: [PATCH] pmem: export the symbols
__copy_user_flushcache and __copy_from_user_flushcache)
On Thu, 24 Sep 2020, Mikulas Patocka wrote:
> On Tue, 22 Sep 2020, Matthew Wilcox wrote:
>
> > > There is a small window when renamed inode is neither in source nor in
> > > target directory. Fsck will reclaim such inode and add it to lost+found -
> > > just like on EXT2.
> >
> > ... ouch. If you have to choose, it'd be better to link it to the second
> > directory then unlink it from the first one. Then your fsck can detect
> > it has the wrong count and fix up the count (ie link it into both
> > directories rather than neither).
>
> I admit that this is lame and I'll fix it. Rename is not so
> performance-critical, so I can add a small journal for this.
Hi
I have implmemented transactions in nvfs and I use them for rename,
setattr, atomic xattr replacement and for RENAME_EXCHANGE.
You can download the current version here:
git://leontynka.twibright.com/nvfs.git
Mikulas
Powered by blists - more mailing lists