| 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
| ||
|
Message-ID: <alpine.LFD.2.00.1102211640350.5715@dhcp-27-109.brq.redhat.com> Date: Mon, 21 Feb 2011 16:52:45 +0100 (CET) From: Lukas Czerner <lczerner@...hat.com> To: bugzilla-daemon@...zilla.kernel.org cc: linux-ext4@...r.kernel.org Subject: Re: [Bug 29402] New: kernel panics while running ffsb scalability workloads on 2.6.38-rc1 through -rc5 On Fri, 18 Feb 2011, bugzilla-daemon@...zilla.kernel.org wrote: > > These panics can be suppressed by using -E lazy_itable_init at mkfs time. The > test system survived two series of 10 ffsb tests beginning with a single mkfs > each. Subsequently, the system survived a run of about 16 hours in which a > complete scalability measurement pass was made > Hi Eric, Are you saying that it works fine (without panic) with lazy_itable_init feature enabled ? I am confused now, because in the first trace "spinlock bad magic: ext4lazyinit" the ext4lazyinit thread is obviously running. When the ext4lazyinit thread is running, it means that inode table was not zeroed, hence kernel thread (ext4lazyinit) is trying to do the job. Am I missing something ? Note that on the kernel which supports lazy itable initialization (/sys/fs/ext4/features/lazy_itable_init exists) the mke2fs (since v1.41.12-50-g210fd2c) will skip inode table initialization automatically (it is the same as you would specify -E lazy_itable_init). Thanks! -Lukas -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists