linux-ext4 - [Bug 216229] New: Same content in two different files - strange problem, unsure if caused by kernel housekeeping

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-216229-13602@https.bugzilla.kernel.org/>
Date:   Sat, 09 Jul 2022 18:22:23 +0000
From:   bugzilla-daemon@...nel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 216229] New: Same content in two different files - strange
 problem, unsure if caused by kernel housekeeping

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

            Bug ID: 216229
           Summary: Same content in two different files - strange problem,
                    unsure if caused by kernel housekeeping
           Product: File System
           Version: 2.5
    Kernel Version: Linux version 5.15.51-i7 (root@...nk3) (gcc (Debian
                    8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian)
                    2.31.1) #1 SMP PREEMPT Thu Jun 30 09:55:14 CEST 2022
          Hardware: IA-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext2
          Assignee: fs_ext2@...nel-bugs.osdl.org
          Reporter: joerg.sigle@...gle.com
        Regression: No

Created attachment 301382
  --> https://bugzilla.kernel.org/attachment.cgi?id=301382&action=edit
two consecutively written files on ext2 (by ext4) end up with the same content
when written from the same bash script and ls is not called afterwards from
therein, too

I might have found a problem where two consecutively written files on ext2 (by
ext4) end up with the same content when written from the same bash script - but
NOT if ls is called right thereafter before that same script ends. --- Sounds
strange and possibly scary to me. Might still be a problem of my own, but I
observed it on ext2, and not on ntfs-3g in the same system, and never in many
years before. --- Please see the attached plain text (but better formatted)
description for further information. Thank you.

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

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