Re: 2.6.20: reproducible hard lockup with RAID-5 resync

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sunday February 18, bugfood-ml@xxxxxxxxxx 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
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux