linux-ext4 - [Bug 217888] New: jbd2: potential data lost in recovering journal raced with synchronizing fs bdev

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: <bug-217888-13602@https.bugzilla.kernel.org/>
Date:   Fri, 08 Sep 2023 08:12:58 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 217888] New: jbd2: potential data lost in recovering journal
 raced with synchronizing fs bdev

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

            Bug ID: 217888
           Summary: jbd2: potential data lost in recovering journal raced
                    with synchronizing fs bdev
           Product: File System
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: chengzhihao1@...wei.com
        Regression: No

1. Apply diff and compile kernel
2. dd if=disk_1 of=/dev/sda bs=1M
   dd if=disk_1 of=/dev/sda bs=1M seek=43
3. mount /dev/sda temp # will stuck
4. sync /dev/sda # Type this command in another terminal, finish it in 5s when
you see "wait sync" from dmesg.
4. umount temp
5. fsck.ext4 -fn /dev/sda


Unattached inode 13
Connect to /lost+found? no

Pass 5: Checking group summary information

/dev/sda: ********** WARNING: Filesystem still has errors **********



===============
'touch file' is recorded in journal of sda, and the journal is not replayed
yet.

journal in sda:

Journal starts at block 1, transaction 2
Found expected sequence 2, type 1 (descriptor block) at block 1
Dumping descriptor block, sequence 2, at block 1:
  FS block 266 logged at journal block 2 (flags 0x0)
  FS block 2 logged at journal block 3 (flags 0x2)
  FS block 276 logged at journal block 4 (flags 0x2)   # new inode
  FS block 273 logged at journal block 5 (flags 0x2)
  FS block 3479 logged at journal block 6 (flags 0x2)  # new dentry
  FS block 1 logged at journal block 7 (flags 0xa)
Found expected sequence 2, type 2 (commit block) at block 8

-- 
You may reply to this email to add a comment.

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