From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org, nfsv4@linux-nfs.org
Cc: linux-kernel@vger.kernel.org
Subject: nfs server patches not in 2.6.25
Date: Fri, 25 Jan 2008 19:15:10 -0500 [thread overview]
Message-ID: <20080126001510.GH25141@fieldses.org> (raw)
In-Reply-To: <20080125231521.GG25141@fieldses.org>
Just some idea what we might be working on for 2.6.26, besides continued
bug-fixing and cleanup:
Work that we already have patches for and that I expect to be included
in whole or in 2.6.26:
- ipv6: Aurélien Charbon's patch to add ipv6 support to the
server's export interface is ready. I'm not clear what else
remains for full ipv6 support.
- failover and migration: Wendy Cheng's patches appear to be in
good shape, so I expect them or something with equivalent
functionality to be in 2.6.26.
- gss callbacks: We have patches to add support for rpcsec_gss
on NFSv4's callback channel (allowing us to support
delegations on kerberos mounts), but they've been put on hold
pending improvements to the client's gssd upcall. I hope to
get back to that work in the next few weeks.
Also in progress:
- spkm3 and future gss mechanisms may generate context
initiation rpc's that are very large. Olga Kornievskaia and I
have been working on fixing the server gssd interfaces to
permit this.
- There are some mismatches between the semantics required for
nfsv4 delegations and what Linux's lease subsystem provides
us. David Richter and I have done a little work on this. We
need to start submitting it.
Three items I identified previously as issues I'd like fixed before we
removed the dependency of CONFIG_NFSD_V4 on CONFIG_EXPERIMENTAL:
http://linux-nfs.org/pipermail/nfsv4/2006-December/005497.html
- export paths consistent between v2/v3/v4: We have some code
that fixes this entirely in userspace. That approach doesn't
provide stable filehandles in the NFSv4 pseudofilesystem, and
there seems to be a general sentiment that it's overly
complicated. It has the one advantage that we don't have to
commit to it, since it uses only existing kernel interfaces.
So I think we're probably going to apply that to nfs-utils as
a stopgap measure and start work on fixing this in the kernel
at the same time....
- reboot recovery: there have been complaints about the
server-side nfsv4 reboot recovery code for a while, we've had
code that tries to fix it for a while, and it just hasn't
happened. I'm hoping we can finally get this ready for
2.6.26.
- export security: this was finished in 2.6.23; we now support
export options like sec=krb5:krb5i:krb5p, which have a few
advantages over the special gss/krb5 client names. This could
be better documented, though.
I've probably left a lot out. Let me know of ongoing projects and
todo's that I've forgotten....
--b.
next prev parent reply other threads:[~2008-01-26 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 23:15 nfs server patches for 2.6.25 J. Bruce Fields
2008-01-26 0:15 ` J. Bruce Fields [this message]
2008-01-27 20:42 ` Simon Holm Thøgersen
2008-01-27 22:10 ` J. Bruce Fields
2008-01-28 3:15 ` 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=20080126001510.GH25141@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@linux-nfs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox