linux-ext4 - Re: [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write

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:	Mon, 11 Oct 2010 14:43:58 -0600
From:	Andreas Dilger <adilger.kernel@...ger.ca>
To:	Christian Casteyde <casteyde.christian@...e.fr>
Cc:	linux-ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [Bug 17361] Watchdog detected hard LOCKUP in jbd2_journal_get_write_access


On 2010-10-02, at 09:42, Theodore Tso <tytso@....edu> wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=17361
> 
> Except for the initial bug report, none of the other stack traces have anything to do with ext4/jbd2.    And in the initial ext4 trace, we see the complaint that we're calling might_sleep() in ext4_mark_inode_dirty(), in a code path where we are manifestly not taking any spinlocks.    And in fact we don't see any spinlocks being taken at the point where the complaint is mode in ext4_mark_inode_dirty().   Yet preempt_count > 1.

In my experience, this is typically caused by stack overflow smashing the task struct and randomly setting preempt_count to a non-zero value.

Cheers, Andreas





--
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