From: Boaz Harrosh <bharrosh@panasas.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>, Stable Tree <stable@kernel.org>
Cc: Randy Dunlap <rdunlap@xenotime.net>
Subject: [PATCHSET 0/4] ore: Kernel 3.3 BUG squashing (Also for 3.2 Stable@)
Date: Fri, 6 Jan 2012 16:37:22 +0200 [thread overview]
Message-ID: <4F070722.8030907@panasas.com> (raw)
October's large testing has unearthed some nasty bugs. Do to
my Deficiency I have failed to send them for the 3.2 Kernel,
so here they are for the 3.3 Merge window, and also for
the Stable@ tree.
Sorry!
[PATCH 1/4] ore: FIX breakage when MISC_FILESYSTEMS is not set
Random Kconfig breakage found by Randy Dunlap. Thanks Randy.
[PATCH 2/4] ore: Fix crash in case of an IO error.
[PATCH 3/4] ore: fix BUG_ON, too few sgs when reading
[PATCH 4/4] ore: Must support none-PAGE-aligned IO
All these are BUG_ON(s) and crashes. Most interesting
is the last one which proves that the 3.2 RAID engine
was a bit premature.
After this code both exofs and pNFS pass tests including RAID5
verification. Cheers! (exofs did so before pNFS didn't)
Thanks
Boaz
next reply other threads:[~2012-01-06 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 14:37 Boaz Harrosh [this message]
2012-01-06 14:40 ` [PATCH 1/4] ore: FIX breakage when MISC_FILESYSTEMS is not set Boaz Harrosh
2012-01-07 18:19 ` Randy Dunlap
2012-01-06 14:42 ` [PATCH 2/4] ore: Fix crash in case of an IO error Boaz Harrosh
2012-01-06 14:43 ` [PATCH 3/4] ore: fix BUG_ON, too few sgs when reading Boaz Harrosh
2012-01-06 14:46 ` [PATCH 4/4] ore: Must support none-PAGE-aligned IO Boaz Harrosh
2012-01-08 8:50 ` [PATCH 4/4 ver2] " Boaz Harrosh
2012-01-08 8:50 ` [PATCH 4/4] " Boaz Harrosh
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=4F070722.8030907@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=rdunlap@xenotime.net \
--cc=stable@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.