linux-kernel - an infinite loop in ext4 in 3.14

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.02.1404171510330.22570@file01.intranet.prod.int.rdu2.redhat.com>
Date:	Thu, 17 Apr 2014 15:23:13 -0400 (EDT)
From:	Mikulas Patocka <mpatocka@...hat.com>
To:	linux-ext4@...r.kernel.org, "Theodore Ts'o" <tytso@....edu>
cc:	linux-kernel@...r.kernel.org
Subject: an infinite loop in ext4 in 3.14

Hi

I hit a bug in ext4 - jbd2 was stuck in an infinite loop when remounting 
the root filesystem read-only during shutdown.

The filesystem is ext3, but it uses the ext4 driver with the following 
options: rw,relatime,discard,errors=remount-ro,data=ordered

The machine was stuck, but it was possible to obtain a stacktrace with 
Alt-SysRQ-P. I put several stacktraces here:

http://people.redhat.com/~mpatocka/crashes/ext4/

The stacktraces change in jbd2_log_do_checkpoint and 
jbd2_cleanup_journal_tail. jbd2_log_do_checkpoint doesn't call 
jbd2_cleanup_journal_tail from a loop, so the the probable location of the 
infinite loop was this piece of code in jbd2_journal_flush:

while (!err && journal->j_checkpoint_transactions != NULL) {

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