All of lore.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Manish Katiyar <mkatiyar@gmail.com>
Cc: linux-raid@vger.kernel.org, Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
Date: Mon, 7 Nov 2011 09:00:56 +1100	[thread overview]
Message-ID: <20111107090056.66331af5@notabene.brown> (raw)
In-Reply-To: <CAE0An6eSxFBYbHj7M=k4YDJdUv3oP8Y3_Sc3BB7K2RKix0W-yw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 921 bytes --]

On Fri, 4 Nov 2011 11:25:41 -0700 Manish Katiyar <mkatiyar@gmail.com> wrote:

> On Mon, Oct 31, 2011 at 11:29 PM, NeilBrown <neilb@suse.de> wrote:
> > On Mon, 31 Oct 2011 23:09:04 -0700 Manish Katiyar <mkatiyar@gmail.com> wrote:
> >
> >> > I think you were quite unlucky to hit this and that you will find it hard to
> >> > reproduce. :-(
> >>
> >> Well, its always reproducible on my ubuntu when I run that script.
> >>
> >
> > Excellent!!   That means you can reliably see if the patch fixes it. :-)
> 
> Sorry for the late reply. Yes it fixes it for me.

Thanks a lot for the confirmation!

NeilBrown


> 
> 
> 
> >
> > I guess I was thinking of 'real' devices which are slower than XOR.  You were
> > using loop back device on files in /tmp which are presumably always in memory.
> > I guess it would be a lot easier to hit in that case.
> >
> > Thanks,
> > NeilBrown
> >
> 
> 
> 


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2011-11-06 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 21:29 [PANIC] : kernel BUG at drivers/md/raid5.c:2756! Manish Katiyar
2011-11-01  5:39 ` NeilBrown
2011-11-01  6:09   ` Manish Katiyar
2011-11-01  6:29     ` NeilBrown
2011-11-04 18:25       ` Manish Katiyar
2011-11-06 22:00         ` NeilBrown [this message]
2011-11-04 19:03   ` Williams, Dan J
2011-11-06 22:12     ` NeilBrown

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=20111107090056.66331af5@notabene.brown \
    --to=neilb@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mkatiyar@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 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.