From: NeilBrown <neilb@suse.de>
To: Karl Newman <siliconfiend@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [BISECT] Kernel panic, RIP bitmap_create
Date: Fri, 4 May 2012 16:47:38 +1000 [thread overview]
Message-ID: <20120504164738.3ddf4073@notabene.brown> (raw)
In-Reply-To: <CAOOwNtKko_db_wtqYOiGScq0ZOMbMK1L9DhDnm1geWhsQmLWNQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
On Thu, 3 May 2012 23:37:38 -0700 Karl Newman <siliconfiend@gmail.com> wrote:
> Somehow gmail marked this email as read, too, so I missed it. Anyway,
> that did it! With this patch applied I can successfully boot! I tested
> the offending commit by itself first with the all-zeros uuid patch
> applied and confirmed the bug was still present, then applied this
> patch and the bug was gone. I also applied this patch to 3.4-rc5 and
> confirmed that it was still good.
Thanks - and good news.
I'd still like to know how this bug manages to cause a crash (I create an
array that have identical "mdadm -E" and "mdadm -X" output on an x86_64
machine, and couldn't make it crash).
I'll add a Reported-by: and Tested-by: for you and submit to Linus shortly.
>
> Thank you for your help on this issue, and thank you for your work as
> a kernel developer and supporting this crucial component.
A pleasure - specially when I get to work with helpful and responsive
people :-)
NeilBrown
>
> Sincerely,
>
> Karl Newman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-04 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAOOwNtJhFa67EFTs5AdgSHzFseBr9xJGTsaEOyYnaYYNCeUMAQ@mail.gmail.com>
2012-05-03 5:05 ` [BISECT] Kernel panic, RIP bitmap_create Karl Newman
2012-05-03 5:58 ` NeilBrown
2012-05-03 6:14 ` Karl Newman
2012-05-03 6:25 ` NeilBrown
2012-05-03 6:50 ` NeilBrown
2012-05-04 6:37 ` Karl Newman
2012-05-04 6:47 ` NeilBrown [this message]
2012-05-04 13:54 ` Karl Newman
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=20120504164738.3ddf4073@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=siliconfiend@gmail.com \
/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).