linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>,
	NFS list <linux-nfs@vger.kernel.org>,
	open-osd <osd-dev@open-osd.org>,
	Benny Halevy <bhalevy@tonian.com>,
	Fred Isaman <iisaman@netapp.com>
Subject: [PATCHSET 0/2] pnfs-obj: Important BUG fixing also for @Stable
Date: Fri, 6 Jan 2012 09:23:58 +0200	[thread overview]
Message-ID: <4F06A18E.4010706@panasas.com> (raw)

Hi Trond

I'm sending in two patches that fixes a bad hung, memory leak, a WARN_ON
and plain wrong protocol handling. In regard to objlayout error handling.
These are also aimed at Stable@ for the 3.2 Kernel.
(Actually these bugs are in since 3.0, I might produce another version
 for 3.[1,0] after these go in)

I have simulated errors at various layers, reads and writes, in combination
of different tests, and they work as I expect. .i.e IO continues to MDS and
oblayout is returned on error.

Please include these patches for 3.3 and they can go to Stable@ for 3.2
has well.

list of patches:
[PATCH 1/2] pnfs-obj: pNFS errors are communicated on iodata->pnfs_error

	This is just a stupidity and neglect. Benny can you understand
	what happened here?

[PATCH 2/2] pnfs-obj: Must return layout on IO error

	This patch is mainly for pnfs.c but I think it is very simple
	and totally not affecting anybody but objlayout. So it should
	be safe, and does fixes my main problem.
	Fred please review?

Please Review

Thanks
Boaz

             reply	other threads:[~2012-01-06  7:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06  7:23 Boaz Harrosh [this message]
2012-01-06  7:28 ` [PATCH 1/2] pnfs-obj: pNFS errors are communicated on iodata->pnfs_error Boaz Harrosh
2012-01-06  7:31 ` [PATCH 2/2] pnfs-obj: Must return layout on IO error Boaz Harrosh
2012-01-09  8:09 ` [PATCHSET 0/2] pnfs-obj: Important BUG fixing also for @Stable Benny Halevy

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=4F06A18E.4010706@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bhalevy@tonian.com \
    --cc=iisaman@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=osd-dev@open-osd.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).