linux-kernel - Re: boot panic after oops from sysfs_new

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 01 Sep 2009 16:14:49 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Meelis Roos <mroos@...ux.ee>
CC:	David Miller <davem@...emloft.net>, sparclinux@...r.kernel.org,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: boot panic after oops from sysfs_new_dirent

Meelis Roos wrote:
>>> I powered on my 6-CPU E3000 after a summer pause and tried todays 
>>> 2.6.31-rc8+git on it. It fails - first it spills lots of warnings about 
>>> percpu things, then oopses in sysfs_new_dirent and then panics.
> 
> Bisecting shows that there may be different crashes, like in
> 56513ed50cc8a5c184a3f347e81d74c850cc14fa below:

Yeah, I was trying to fix that one with
74d46d6b2d23d44d72c37df4c6a5d2e782f7b088 and it seemingly fixed it on
my machine.  Apparently broken on yours.  Are the errors different
before and after 74d46d6b2d?

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/