From: Benny Halevy <bhalevy@tonian.com>
To: Jim Rees <rees@umich.edu>
Cc: linux-nfs@vger.kernel.org, peter honeyman <honey@citi.umich.edu>
Subject: Re: [PATCH 0/3] three bug fixes
Date: Wed, 21 Sep 2011 16:37:37 +0300 [thread overview]
Message-ID: <4E79E8A1.5060806@tonian.com> (raw)
In-Reply-To: <1316489025-24991-1-git-send-email-rees@umich.edu>
On 2011-09-20 06:23, Jim Rees wrote:
> This patch set fixes three bugs found in pnfsblock testing.
>
> Peng Tao (3):
> pnfsblock: fix NULL pointer dereference
> pnfsblock: fix writeback deadlock
> nfs4: serialize layoutcommit
>
> fs/nfs/blocklayout/blocklayout.c | 11 +++++++++--
> fs/nfs/nfs4proc.c | 6 ++++++
> fs/nfs/pnfs.c | 24 +++++++++++++++++++++---
> include/linux/nfs_fs.h | 1 +
> 4 files changed, 37 insertions(+), 5 deletions(-)
>
Submitted these too,
Thanks!
Benny
prev parent reply other threads:[~2011-09-21 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 3:23 [PATCH 0/3] three bug fixes Jim Rees
2011-09-20 3:23 ` [PATCH 1/3] pnfsblock: fix NULL pointer dereference Jim Rees
2011-09-20 3:23 ` [PATCH 2/3] pnfsblock: fix writeback deadlock Jim Rees
2011-09-20 3:23 ` [PATCH 3/3] nfs4: serialize layoutcommit Jim Rees
2011-09-21 13:37 ` Benny Halevy [this message]
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=4E79E8A1.5060806@tonian.com \
--to=bhalevy@tonian.com \
--cc=honey@citi.umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=rees@umich.edu \
/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).