linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Corey Hickey <bugfood-ml@fatooh.org>
To: linux-raid@vger.kernel.org
Subject: Re: 2.6.20: reproducible hard lockup with RAID-5 resync
Date: Sun, 18 Feb 2007 13:09:53 -0800	[thread overview]
Message-ID: <45D8C0A1.6090903@fatooh.org> (raw)
In-Reply-To: <45D8219E.9080603@fatooh.org>

Corey Hickey wrote:
> Corey Hickey wrote:
>> I think I have found an easily-reproducible bug in Linux 2.6.20. I have
>> already applied the "Fix various bugs with aligned reads in RAID5"
>> patch, and that had no effect. It appears to be related to the resync
>> process, and makes the system lock up, hard.
> 
> I now have a different build of 2.6.20 running resync without the
> reported problem. I'll try to isolate the specific difference between
> the two builds some time tomorrow.

Ok, so the difference is CONFIG_SYSFS_DEPRECATED. If that is not
defined, the kernel locks up. There's not a lot of code under
#ifdef/#ifndef CONFIG_SYSFS_DEPRECATED, but since I'm not familiar with
any of it I don't expect trying to locate the bug on my own would be
very productive.

Neil, do you have CONFIG_SYSFS_DEPRECATED enabled? If so, does disabling
it reproduce my problem? If you can't reproduce it, should it take the
problem over to linux-kernel?

Thanks,
Corey

  reply	other threads:[~2007-02-18 21:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16  6:47 2.6.20: reproducible hard lockup with RAID-5 resync Corey Hickey
2007-02-16  7:59 ` Neil Brown
2007-02-16  8:11   ` Corey Hickey
2007-02-16 21:23   ` Corey Hickey
2007-02-17 10:58     ` Corey Hickey
2007-02-17 11:14       ` Justin Piszcz
2007-02-17 19:19         ` Corey Hickey
2007-02-18  9:51 ` Corey Hickey
2007-02-18 21:09   ` Corey Hickey [this message]
2007-02-18 22:04     ` Neil Brown
2007-02-19  0:06       ` Corey Hickey

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=45D8C0A1.6090903@fatooh.org \
    --to=bugfood-ml@fatooh.org \
    --cc=linux-raid@vger.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 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).