From: Christoph Hellwig <hch@infradead.org>
To: linux-nfs@vger.kernel.org
Subject: nfsd4_is_junction
Date: Sat, 29 Oct 2011 06:16:49 -0400 [thread overview]
Message-ID: <20111029101649.GA12345@infradead.org> (raw)
This function should probably grow a check for S_NOSEC instead of
hitting the filesystems with an xattr read for every lookup.
next reply other threads:[~2011-10-29 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 10:16 Christoph Hellwig [this message]
2011-10-29 17:45 ` nfsd4_is_junction J. Bruce Fields
2011-11-02 8:30 ` nfsd4_is_junction Christoph Hellwig
2011-10-29 17:47 ` nfsd4_is_junction Chuck Lever
2011-10-29 17:55 ` nfsd4_is_junction J. Bruce Fields
2011-10-29 17:58 ` nfsd4_is_junction Chuck Lever
2011-10-29 18:09 ` nfsd4_is_junction J. Bruce Fields
2011-10-29 18:38 ` nfsd4_is_junction Chuck Lever
2011-10-29 23:36 ` nfsd4_is_junction Trond Myklebust
2011-10-31 15:09 ` nfsd4_is_junction Chuck Lever
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=20111029101649.GA12345@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.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.