From: NeilBrown <neilb@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: [PATCH 000 of 5] knfsd: Introduction - bugfixes for 2.6.19
Date: Tue, 17 Oct 2006 09:30:04 +1000 [thread overview]
Message-ID: <20061017092702.11224.patches@notabene> (raw)
Following 5 patches for nfsd/lockd are bug fixes that are appropriate for
2.6.19 (matches made against 2.6.18-rc1-mm1).
Thanks,
NeilBrown
[PATCH 001 of 5] knfsd: nfsd4: fix owner-override on open
[PATCH 002 of 5] knfsd: nfsd4: fix open permission checking
[PATCH 003 of 5] knfsd: nfsd4: Fix error handling in nfsd's callback client
[PATCH 004 of 5] knfsd: Fix bug in recent lockd patches that can cause reclaim to fail.
[PATCH 005 of 5] knfsd: Allow lockd to drop replys as appropriate.
next reply other threads:[~2006-10-16 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 23:30 NeilBrown [this message]
2006-10-16 23:30 ` [PATCH 001 of 5] knfsd: nfsd4: fix owner-override on open NeilBrown
2006-10-16 23:30 ` [PATCH 002 of 5] knfsd: nfsd4: fix open permission checking NeilBrown
2006-10-16 23:30 ` [PATCH 003 of 5] knfsd: nfsd4: Fix error handling in nfsd's callback client NeilBrown
2006-10-16 23:30 ` [PATCH 004 of 5] knfsd: Fix bug in recent lockd patches that can cause reclaim to fail NeilBrown
2006-10-16 23:30 ` [PATCH 005 of 5] knfsd: Allow lockd to drop replys as appropriate NeilBrown
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=20061017092702.11224.patches@notabene \
--to=neilb@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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