From: David Howells <dhowells@redhat.com>
To: viro@zeniv.linux.org.uk
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/8] afs: Network-namespacing
Date: Wed, 23 May 2018 13:16:41 +0100 [thread overview]
Message-ID: <152707780120.27887.10118775145086304138.stgit@warthog.procyon.org.uk> (raw)
Hi Al,
Can you pull these patches on top of Christoph's procfs changes? The patches
do:
(*) Rearrange fs/afs/proc.c to get rid of the forward declarations and
simplify the commenting.
(*) Supply functions that allow writable net proc files to be created
(this could be extended to provide writing on non-net proc files).
(*) Implement network namespacing in AFS and simplify the proc usage,
using the new convenience functions provided.
I've included another couple of small patches also:
(*) afs_net::ws_cell should be annotated and accessed for RCU. This patch
would conflict with the other patches if separate.
(*) Fix a sparse warning where sparse can't manage to follow the locking
in a function.
Note that these patches don't quite complete network namespacing; the last
bit requires the mount API patches to allow propagation of the network
namespace across automounts.
The patches are tagged here:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git
afs-namespace-20180523
The patches can be found here also:
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=afs-namespace
David
---
David Howells (8):
afs: Move /proc management functions to the end of the file
afs: Rearrange fs/afs/proc.c by moving fops and open functions down
afs: Rearrange fs/afs/proc.c to move the show routines up
afs: Rearrange fs/afs/proc.c to remove remaining predeclarations.
proc: Add a way to make network proc files writable
afs: Fix a Sparse warning in xdr_decode_AFSFetchStatus()
afs: Mark afs_net::ws_cell as __rcu and set using rcu functions
afs: Implement network namespacing
fs/afs/cell.c | 12 -
fs/afs/cmservice.c | 2
fs/afs/fsclient.c | 97 +++---
fs/afs/internal.h | 45 +--
fs/afs/main.c | 33 ++
fs/afs/netdevices.c | 6
fs/afs/proc.c | 787 +++++++++++++++++------------------------------
fs/afs/rxrpc.c | 2
fs/afs/super.c | 20 +
fs/proc/generic.c | 24 +
fs/proc/internal.h | 2
fs/proc/proc_net.c | 92 +++++
include/linux/proc_fs.h | 12 +
13 files changed, 552 insertions(+), 582 deletions(-)
next reply other threads:[~2018-05-23 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-23 12:16 David Howells [this message]
2018-05-23 12:16 ` [PATCH 1/8] afs: Move /proc management functions to the end of the file David Howells
2018-05-23 12:16 ` [PATCH 2/8] afs: Rearrange fs/afs/proc.c by moving fops and open functions down David Howells
2018-05-23 12:17 ` [PATCH 3/8] afs: Rearrange fs/afs/proc.c to move the show routines up David Howells
2018-05-23 12:17 ` [PATCH 4/8] afs: Rearrange fs/afs/proc.c to remove remaining predeclarations David Howells
2018-05-23 12:17 ` [PATCH 5/8] proc: Add a way to make network proc files writable David Howells
2018-05-23 12:17 ` [PATCH 6/8] afs: Fix a Sparse warning in xdr_decode_AFSFetchStatus() David Howells
2018-05-23 12:17 ` [PATCH 7/8] afs: Mark afs_net::ws_cell as __rcu and set using rcu functions David Howells
2018-05-23 12:17 ` [PATCH 8/8] afs: Implement network namespacing 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=152707780120.27887.10118775145086304138.stgit@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=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).