From: Andreas Gruenbacher <agruen@suse.de>
To: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/11] nfsacl
Date: Mon, 26 Apr 2004 12:28:47 +0200 [thread overview]
Message-ID: <1082975143.3295.68.camel@winden.suse.de> (raw)
Hello,
this is the nfsacl protocol extension that implements setting/retrieving
acls over NFSv3. (It has nothing to do with NFSv4 acls, which are very
different.) Any chance we can get this into -mm, and into mainline after
some more exposure? The patches are:
sunrpc-enosys-when-unavail
Differentiate between program/procedure not available and
other errors. Required so that nfs clients know whether or
not the server supports nfsacl.
sunrpc-multiple-programs
Support multiple program numbers on one RPC transport. The nfs
and nfsacl RPC programs both run on the same transport, so
we need to multiplex.
rpcsvc-pages
Add a page to an rpc reply from the allocated pool.
sunrpc-xdr-words
Encode 32-bit words in xdr_buf's. The code is modeled after the
decode functions already in 2.6.6-rc2.
sunrpc-xdr-arrays
sunrpc: Encode/decode arrays that may become large.
nfsacl-lazy-alloc
Allow to allocate pages in the receive buffers lazily. ACLs may have
up to 1024 entries in nfsacl but usually are small, so allocating
space for them on demand makes sense.
nfs-access-acl
NFS mount parameter noacl: Allow clients to mount without using
the ACCESS remote procedure call.
qsort
Add qsort, needed for decoding acls from nfsacl.
xfs-no-qsort
Remove qsot from xfs. Without, qsort would be defined twice in the
kernel.
nfsd-acl
Server nfsacl support.
nfs-acl
Client nfsacl support.
Cheers,
--
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX AG
next reply other threads:[~2004-04-26 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 10:28 Andreas Gruenbacher [this message]
2004-04-27 15:18 ` [PATCH 0/11] nfsacl J. Bruce Fields
2004-04-27 15:51 ` Andreas Gruenbacher
2004-04-27 16:12 ` J. Bruce Fields
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=1082975143.3295.68.camel@winden.suse.de \
--to=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@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.