linux-ext4 - [Bug 200069] BUG() triggered in start_this_handle() (jbd2/transaction.c) when operating and umounting a crafted ext4 image

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: <bug-200069-13602-ZgjFd46Tpz@https.bugzilla.kernel.org/>
Date:   Fri, 15 Jun 2018 14:13:30 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 200069] BUG() triggered in start_this_handle()
 (jbd2/transaction.c) when operating and umounting a crafted ext4 image

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

--- Comment #3 from Wen Xu (wen.xu@...ech.edu) ---
Created attachment 276575
  --> https://bugzilla.kernel.org/attachment.cgi?id=276575&action=edit
A simplified image

I feel hard to simplify this corrupted image but meanwhile still keep hitting
the BUG(). Right now I just upload a simplified image that leads to this error
by poc.c:

[  516.384286] EXT4-fs (loop0): mounted filesystem with ordered data mode.
Opts: (null)
[  531.719394] jbd2_journal_bmap: journal block not found at offset 7 on
loop0-8
[  531.721009] Aborting journal on device loop0-8.
[  531.851971] EXT4-fs error (device loop0): ext4_journal_check_start:61:
Detected aborted journal
[  531.854414] EXT4-fs (loop0): Remounting filesystem read-only

-- 
You are receiving this mail because:
You are watching the assignee of the bug.