linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	NFS list <linux-nfs@vger.kernel.org>,
	open-osd <osd-dev@open-osd.org>
Subject: [GIT PULL] exofs/ore: BUG fixes for the 3.3 merge window
Date: Mon, 9 Jan 2012 13:50:21 +0200	[thread overview]
Message-ID: <4F0AD47D.2020405@panasas.com> (raw)

Linus hi.

the following changes since Linux 3.2-rc7

are available in the git repository at:
  git://git.open-osd.org/linux-open-osd.git for-linus

All of these are actually BUGS to the 3.2 Kernel and therefor CCed
to the Stable@kernel.org.
(I'm really sorry that I did not have them ready before)

They fix a rand-config breakage and some BUG_ONs and crashes,
which where unearthed during some large scale testing. With
these I'm back to a usable system, including RAID5 introduced
in 3.2.

Boaz Harrosh (4):
      ore: FIX breakage when MISC_FILESYSTEMS is not set
      ore: Fix crash in case of an IO error.
      ore: fix BUG_ON, too few sgs when reading
      ore: Must support none-PAGE-aligned IO

 fs/Kconfig           |    2 +
 fs/exofs/Kconfig     |   11 -------
 fs/exofs/Kconfig.ore |   12 ++++++++
 fs/exofs/ore.c       |    8 ++--
 fs/exofs/ore_raid.c  |   78 +++++++++++++++++++++++++++++++++++++++++--------
 5 files changed, 83 insertions(+), 28 deletions(-)
 create mode 100644 fs/exofs/Kconfig.ore

Thanks, have a good merge window
Boaz

                 reply	other threads:[~2012-01-09 11:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4F0AD47D.2020405@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=osd-dev@open-osd.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).