From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Mike Snitzer <snizer@redhat.com>,
James Bottomley <James.Bottomley@suse.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Ingo Molnar <mingo@elte.hu>
Subject: [Regression] Please revert a91a2785b20
Date: Tue, 29 Mar 2011 00:35:20 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1103290006070.2774@localhost6.localdomain6> (raw)
Out of the blue all my perfectly fine working test machines which use
RAID stopped working with the very helpful error message:
md/raid1:md1: active with 2 out of 2 mirrors
md: pers->run() failed ...
Reverting a91a2785b20 fixes the problem.
Neither the subject line:
block: Require subsystems to explicitly allocate bio_set integrity mempool
nor the changelog have any hint why that wreckage is in any way
sensible.
The wreckage happens due to:
- md_integrity_register(mddev);
- return 0;
+ return md_integrity_register(mddev);
But the changelog does not give the courtesy of explaining these
changes. Also there is no fcking reason why the kernel cannot deal
with the missing integrity capabilities of a drive just by emitting a
warning msg and dealing gracefully with the outcome.
All my RAID setups have been working perfectly fine until now, so
what's the rationale to break this?
Did anyone test this shite on a non enterprise class hardware with a
distro default config ? Obviously _NOT_.
FYI, the config files of those machines are based off a fedora default
config, so this would hit all raid users based on popular distro
configs sooner than later.
Thanks for stealing my time,
tglx
next reply other threads:[~2011-03-28 22:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 22:35 Thomas Gleixner [this message]
2011-03-28 22:43 ` Thomas Gleixner
2011-03-28 23:03 ` Mike Snitzer
2011-03-29 6:59 ` Jens Axboe
2011-03-29 13:20 ` Mike Snitzer
2011-03-29 13:35 ` James Bottomley
2011-03-29 13:42 ` Martin K. Petersen
2011-03-29 13:58 ` Need to refactor DM's integrity profile support a bit (was: Re: Please revert a91a2785b20) Mike Snitzer
2011-04-01 17:42 ` [PATCH] dm: improve block integrity support Mike Snitzer
2011-04-14 14:09 ` Mike Snitzer
2011-04-14 14:42 ` Mike Snitzer
2011-04-15 4:57 ` Martin K. Petersen
2011-04-05 2:09 ` Please revert a91a2785b20 NeilBrown
2011-03-28 22:45 ` [Regression] " Martin K. Petersen
2011-03-28 23:03 ` Thomas Gleixner
2011-03-29 0:09 ` Martin K. Petersen
2011-03-29 0:11 ` Martin K. Petersen
2011-03-29 2:32 ` Thomas Gleixner
2011-03-29 5:32 ` Giacomo Catenazzi
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=alpine.LFD.2.00.1103290006070.2774@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=James.Bottomley@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=snizer@redhat.com \
--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
all inboxes | Powered by JetHome®