linux-ext4 - [Bug 29402] kernel panics while running ffsb scalability workloads on 2.6.38-rc1 through -rc5

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]

Message-Id: <201102220410.p1M4AYr4019669@demeter2.kernel.org>
Date:	Tue, 22 Feb 2011 04:10:34 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 29402] kernel panics while running ffsb scalability workloads
 on 2.6.38-rc1 through -rc5

https://bugzilla.kernel.org/show_bug.cgi?id=29402

--- Comment #3 from Eric Whitney <eric.whitney@...com>  2011-02-22 04:10:33 ---
Hi, Lukas:

Unfortunately, I omitted the argument, and that's what's confusing you.   I'm
saying that it works fine - no panic - with the feature disabled:  -E
lazy_itable_init=0.  (I'm sorry about that.  I was filing just a little too
quickly after informing Ted via IRC.  It's been a long hunt.)  Again, it panics
easily with lazy_itable_init set to its default, which means without using the
switch.

In addition to what I initially reported, I've made more than 80 additional
ffsb runs on freshly made ext4, ext4 nojournal, and ext4 mblk_io_submit
filesystems over the last three days with lazy_itable_init=0, and there have
been no further panics.

For the record, I'm using e2fsprogs 1.41.14 straight from Ted's git tree.

Thanks,
Eric

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
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