From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Josef Bacik <josef@redhat.com>
Cc: "Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
linux-btrfs@vger.kernel.org, hch@infradead.org
Subject: Re: [RFC] [PATCH 2/2] Btrfs: move over to use ->update_time
Date: Wed, 04 Apr 2012 13:47:47 -0400 [thread overview]
Message-ID: <1333561669.12904.0.camel@falcor> (raw)
In-Reply-To: <20120404174300.GB2097@localhost.localdomain>
On Wed, 2012-04-04 at 13:43 -0400, Josef Bacik wrote:
> On Wed, Apr 04, 2012 at 08:24:19PM +0300, Kasatkin, Dmitry wrote:
> > Hello,
> >
> > Mimi and I working on IMA/EVM (security/integrity) and it uses
> > i_version for checking if file content has been changed.
> > extX file systems support i_version updates with mounting file system
> > with "iversion" option or via kernel command line parameter
> > "i_version"
> >
> > It seems iversion option is not recognized when mounting btrfs.
> > I see this patchset deals with i_version update as well..
> > Can you please give an advice how to use i_version with btrfs?
> >
>
> Oh good somebody uses this? We actually have a ->sequence thing we use for
> this, the grand idea was to make it smarter about telling nfs when something
> changed, but if you guys use i_version we could probably get rid of our in-core
> sequence and use the normal inodes i_version and then just store it in our
> sequence field on disk. I'll do it without a mount option tho so it just works,
> does that sound good to you? Thanks,
>
> Josef
Sounds really good!
thanks,
Mimi
next prev parent reply other threads:[~2012-04-04 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 14:10 [RFC] [PATCH 1/2] fs: introduce inode operation ->update_time Josef Bacik
2012-03-26 14:10 ` [RFC] [PATCH 2/2] Btrfs: move over to use ->update_time Josef Bacik
2012-04-04 17:24 ` Kasatkin, Dmitry
2012-04-04 17:43 ` Josef Bacik
2012-04-04 17:47 ` Mimi Zohar [this message]
2012-04-04 18:12 ` Kasatkin, Dmitry
2012-04-04 18:16 ` Josef Bacik
2012-04-04 18:21 ` Kasatkin, Dmitry
2012-04-09 15:16 ` J. Bruce Fields
2012-04-10 7:48 ` David Sterba
2012-04-12 11:09 ` Kasatkin, Dmitry
2012-04-12 11:32 ` David Sterba
2012-04-12 11:43 ` Kasatkin, Dmitry
2012-05-11 6:06 ` Kasatkin, Dmitry
2012-05-11 18:34 ` Josef Bacik
2012-04-30 15:21 ` [RFC] [PATCH 1/2] fs: introduce inode operation ->update_time Christoph Hellwig
2012-04-30 17:12 ` Josef Bacik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1333561669.12904.0.camel@falcor \
--to=zohar@linux.vnet.ibm.com \
--cc=dmitry.kasatkin@intel.com \
--cc=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).