linux-kernel - Re: KCSAN: data-race in __fat_write_inode / fat12_ent

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: <877dyveq1h.fsf@mail.parknet.co.jp>
Date:   Sat, 04 Apr 2020 15:14:02 +0900
From:   OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:     Dmitry Vyukov <dvyukov@...gle.com>
Cc:     syzbot <syzbot+6f1624f937d9d6911e2d@...kaller.appspotmail.com>,
        Marco Elver <elver@...gle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: KCSAN: data-race in __fat_write_inode / fat12_ent_get

Dmitry Vyukov <dvyukov@...gle.com> writes:

> On Fri, Apr 3, 2020 at 3:36 PM OGAWA Hirofumi
> <hirofumi@...l.parknet.co.jp> wrote:
>>
>> Hm, looks like the race between a directory entry vs a FAT entry.  This
>> bug was happened with the corrupted image? Or the image passes the check
>> of dosfsck?
>>
>> If the corrupted image, it may be hard to prevent the all races. Well,
>> anyway, the corrupted image of the report will help to detect this
>> corruption.
>
> From the log, it's this program.
> My bet on a corrupted image. syzkaller does not have format
> descriptions for fat, so it's just random bytes.

You meant I can regenerate a disk image from that log (if so, how)?

If not, for next time, it would be helpful if syzkaller provides the log
to regenerate the corrupted image (or saving a corrupted image) to
reproduce this, then I can try to detect the corruption pattern early.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>