From: Neil Brown <neilb@suse.de>
To: Corey Hickey <bugfood-ml@fatooh.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: 2.6.20: reproducible hard lockup with RAID-5 resync
Date: Mon, 19 Feb 2007 09:04:51 +1100 [thread overview]
Message-ID: <17880.52611.569535.56180@notabene.brown> (raw)
In-Reply-To: message from Corey Hickey on Sunday February 18
On Sunday February 18, bugfood-ml@fatooh.org wrote:
>
> 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?
# CONFIG_SYSFS_DEPRECATED is not set
No, it is not set, and yet it all still works for me.
It is very hard to see how this CONFIG option can make a difference.
Have you double checked that setting it removed the problem and
clearing it causes the problem?
If so, then maybe an email to linux-kernel would be appropriate.
Include the full config..
NeilBrown
next prev parent reply other threads:[~2007-02-18 22:04 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
2007-02-18 22:04 ` Neil Brown [this message]
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=17880.52611.569535.56180@notabene.brown \
--to=neilb@suse.de \
--cc=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).