All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso-3s7WtUTddSA@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	jean-noel.cordenner-6ktuUTfB/bM@public.gmane.org,
	cmm-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
	lkml <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	mk <michael.kerrisk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: MS_I_VERSION added in 2.6.25
Date: Fri, 26 Jun 2009 14:45:22 -0400	[thread overview]
Message-ID: <20090626184522.GF7182@mit.edu> (raw)
In-Reply-To: <20090626171144.GA2282-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>

On Fri, Jun 26, 2009 at 01:11:44PM -0400, Christoph Hellwig wrote:
> On Fri, Jun 26, 2009 at 08:46:34AM +0200, Michael Kerrisk wrote:
> > Hi,
> > 
> > Linux 2.6.25 added the MS_I_VERSION flag for inode versioning. Some
> > text on this should be added to the mount(2) man page. Could someone
> > of you provide a short description of
> > 
> > * What inode versions are used for
> 
> I don't think it should be documented.  It should never have been a
> user-visible option to start with and I'm eventually going to fix that.
> 
> The correct way to do this would be a feature flag in the superblock.

Agreed, the intention was this was something which NFSv4 would request
of the filesystem, by flipping a bit.  I don't see a good reason why a
user would ever want to explicit request 64-bit version numbers, since
they're not even visible to userspace.

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Theodore Tso <tytso@mit.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: mtk.manpages@gmail.com, jean-noel.cordenner@bull.net,
	cmm@us.ibm.com, lkml <linux-kernel@vger.kernel.org>,
	linux-man <linux-man@vger.kernel.org>,
	mk <michael.kerrisk@gmail.com>
Subject: Re: MS_I_VERSION added in 2.6.25
Date: Fri, 26 Jun 2009 14:45:22 -0400	[thread overview]
Message-ID: <20090626184522.GF7182@mit.edu> (raw)
In-Reply-To: <20090626171144.GA2282@infradead.org>

On Fri, Jun 26, 2009 at 01:11:44PM -0400, Christoph Hellwig wrote:
> On Fri, Jun 26, 2009 at 08:46:34AM +0200, Michael Kerrisk wrote:
> > Hi,
> > 
> > Linux 2.6.25 added the MS_I_VERSION flag for inode versioning. Some
> > text on this should be added to the mount(2) man page. Could someone
> > of you provide a short description of
> > 
> > * What inode versions are used for
> 
> I don't think it should be documented.  It should never have been a
> user-visible option to start with and I'm eventually going to fix that.
> 
> The correct way to do this would be a feature flag in the superblock.

Agreed, the intention was this was something which NFSv4 would request
of the filesystem, by flipping a bit.  I don't see a good reason why a
user would ever want to explicit request 64-bit version numbers, since
they're not even visible to userspace.

						- Ted

  parent reply	other threads:[~2009-06-26 18:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26  6:46 MS_I_VERSION added in 2.6.25 Michael Kerrisk
2009-06-26  6:46 ` Michael Kerrisk
     [not found] ` <cfd18e0f0906252346v53594fb5u2b2bd630b12ded8e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-06-26 17:11   ` Christoph Hellwig
2009-06-26 17:11     ` Christoph Hellwig
     [not found]     ` <20090626171144.GA2282-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2009-06-26 18:45       ` Theodore Tso [this message]
2009-06-26 18:45         ` Theodore Tso

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=20090626184522.GF7182@mit.edu \
    --to=tytso-3s7wtutddsa@public.gmane.org \
    --cc=cmm-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
    --cc=jean-noel.cordenner-6ktuUTfB/bM@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michael.kerrisk-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.