All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: David Howells <dhowells@redhat.com>
Cc: viro@zeniv.linux.org.uk, linux-api@vger.kernel.org,
	torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] vfs: syscall: Add fsinfo() to query filesystem information
Date: Wed, 1 Aug 2018 12:28:49 -0400	[thread overview]
Message-ID: <20180801162849.GA9187@thunk.org> (raw)
In-Reply-To: <153314004147.18964.11925284995448007945.stgit@warthog.procyon.org.uk>

On Wed, Aug 01, 2018 at 05:14:01PM +0100, David Howells wrote:
> 
> Some attributes (such as the servers backing a network filesystem) can have
> multiple values.  These can be enumerated by setting params->Nth and
> params->Mth to 0, 1, ... until ENODATA is returned.

How does the caller know whether or not a particular attribute has
multiple values?  Is that a fundamental attribute of a particular
attribute?  (e.g., the documentation for each attribute must state
whether or not that attribute returns multiple attributes or not)

	       	    	      	      - Ted

  reply	other threads:[~2018-08-01 16:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-01 16:13 [PATCH 0/5] VFS: Introduce filesystem information query syscall David Howells
2018-08-01 16:14 ` [PATCH 1/5] vfs: syscall: Add fsinfo() to query filesystem information David Howells
2018-08-01 16:28   ` Theodore Y. Ts'o [this message]
2018-08-01 22:20     ` David Howells
2018-08-01 16:14 ` [PATCH 2/5] afs: Add fsinfo support David Howells
2018-08-01 16:14 ` [PATCH 3/5] vfs: Allow fsinfo() to query what's in an fs_context David Howells
2018-08-01 16:14 ` [PATCH 4/5] vfs: Allow fsinfo() to be used to query an fs parameter description David Howells
2018-08-01 16:14 ` [PATCH 5/5] vfs: Implement parameter value retrieval with fsinfo() David Howells

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=20180801162849.GA9187@thunk.org \
    --to=tytso@mit.edu \
    --cc=dhowells@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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.