From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org
Subject: nfsd bugfixes
Date: Wed, 6 Jan 2010 17:44:55 -0500 [thread overview]
Message-ID: <20100106224455.GA11677@fieldses.org> (raw)
The for-2.6.33 branch at:
git://linux-nfs.org/~bfields/linux.git for-2.6.33
has two new nfsd bugfixes, and one you already have*. Please pull.
--b.
* I'd already pushed out a commit when you took it as a patch, and given
the choice between a duplicate commit and rewinding the branch I
figured the duplicate commit was the lesser evil. Feel free to tell
me I'm doing it all wrong.
Christoph Hellwig (1):
nfsd: make sure data is on disk before calling ->fsync
J. Bruce Fields (1):
nfsd: fix "insecure" export option
Xiaotian Feng (1):
sunrpc: fix peername failed on closed listener
fs/nfsd/nfsfh.c | 2 +-
fs/nfsd/vfs.c | 5 +----
net/sunrpc/svc_xprt.c | 3 ++-
3 files changed, 4 insertions(+), 6 deletions(-)
next reply other threads:[~2010-01-06 22:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 22:44 J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-12 21:05 nfsd bugfixes J. Bruce Fields
2007-11-12 22:08 ` Neil Brown
2007-11-12 22:13 ` J. Bruce Fields
2007-11-12 22:35 ` Neil Brown
2007-11-12 23:17 ` J. Bruce Fields
2007-07-27 21:17 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=20100106224455.GA11677@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).