linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Enke Chen <enkechen@cisco.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Jeff Layton <jlayton@poochiereds.net>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <anna.schumaker@netapp.com>,
	linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] VFS: pass the flag setting by fcntl() to vfs
Date: Mon, 9 May 2016 00:02:48 -0700	[thread overview]
Message-ID: <20160509070248.GA24065@infradead.org> (raw)
In-Reply-To: <c5368586-ba17-11ae-6d48-ee244bedf6f9@cisco.com>

On Sun, May 08, 2016 at 05:50:32PM -0700, Enke Chen wrote:
> As explained in the email, currently the validation of the flags does reach
> the vfs, but the setting does not.

s/vfs/fs/, and yes, that's intentional.

> We have an application that uses the FUSE
> to implement a user-space socket, and the flags are needed.

And that's not a supported use case.

  reply	other threads:[~2016-05-09  7:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ebf888a1-ee45-a79b-6f72-43a8744e0196@cisco.com>
2016-05-05 18:26 ` [PATCH] VFS: pass the flag setting by fcntl() to vfs Enke Chen
2016-05-08 10:40   ` Christoph Hellwig
2016-05-09  0:50     ` Enke Chen
2016-05-09  7:02       ` Christoph Hellwig [this message]
2016-05-09 18:39         ` Enke Chen
2016-05-25 19:03   ` [PATCH RESEND] vfs: " Enke Chen
2016-05-25 19:52     ` Al Viro
2016-05-25 21:16       ` Enke Chen

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=20160509070248.GA24065@infradead.org \
    --to=hch@infradead.org \
    --cc=anna.schumaker@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=enkechen@cisco.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    --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).