From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, yuehaibing@huawei.com,
marc.dionne@auristor.com, linux-afs@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL afs: Development for 5.4
Date: Mon, 16 Sep 2019 12:09:27 +0100 [thread overview]
Message-ID: <16147.1568632167@warthog.procyon.org.uk> (raw)
Hi Linus,
Here's a set of patches for AFS. The first three are trivial, deleting
unused symbols and rolling out a wrapper function.
The fourth and fifth patches make use of the previously added RCU-safe
request_key facility to allow afs_permission() and afs_d_revalidate() to
attempt to operate without dropping out of RCU-mode pathwalk. Under
certain conditions, such as conflict with another client, we still have to
drop out anyway, take a lock and consult the server.
David
---
The following changes since commit f16180739cd18a39a1a45516ac0e65d18a9f100e:
Merge remote-tracking branch 'net/master' into afs-next (2019-09-02 11:43:44 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/afs-next-20190915
for you to fetch changes up to a0753c29004f4983e303abce019f29e183b1ee48:
afs: Support RCU pathwalk (2019-09-02 11:43:54 +0100)
----------------------------------------------------------------
AFS development
Tested-by: Marc Dionne <marc.dionne@auristor.com>
----------------------------------------------------------------
David Howells (3):
afs: Use afs_extract_discard() rather than iov_iter_discard()
afs: Provide an RCU-capable key lookup
afs: Support RCU pathwalk
YueHaibing (2):
afs: remove unused variable 'afs_voltypes'
afs: remove unused variable 'afs_zero_fid'
fs/afs/dir.c | 54 +++++++++++++++++++++++++-
fs/afs/fsclient.c | 6 +--
fs/afs/internal.h | 1 +
fs/afs/security.c | 108 +++++++++++++++++++++++++++++++++++++++++++---------
fs/afs/volume.c | 2 -
fs/afs/yfsclient.c | 6 +--
include/linux/key.h | 14 ++++++-
7 files changed, 162 insertions(+), 29 deletions(-)
next reply other threads:[~2019-09-16 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 11:09 David Howells [this message]
2019-09-19 0:22 ` [GIT PULL afs: Development for 5.4 Linus Torvalds
2019-09-19 0:24 ` Linus Torvalds
2019-09-19 1:55 ` pr-tracker-bot
2019-09-19 6:40 ` David Howells
2019-09-19 9:49 ` David Howells
2019-09-19 13:15 ` Matthew Wilcox
2019-09-19 14:03 ` Ilya Dryomov
2019-09-19 15:05 ` Jeffrey E Altman
2019-09-19 14:24 ` David Howells
2019-09-19 16:29 ` Linus Torvalds
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=16147.1568632167@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=torvalds@linux-foundation.org \
--cc=yuehaibing@huawei.com \
/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).