From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+6f1624f937d9d6911e2d@syzkaller.appspotmail.com>,
Marco Elver <elver@google.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: KCSAN: data-race in __fat_write_inode / fat12_ent_get
Date: Sat, 04 Apr 2020 15:14:02 +0900 [thread overview]
Message-ID: <877dyveq1h.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <CACT4Y+YaM9Qj9V9G7G+aQrmfxfdtyBX4WXXsBamUjyMMpEeEdg@mail.gmail.com> (Dmitry Vyukov's message of "Fri, 3 Apr 2020 18:36:26 +0200")
Dmitry Vyukov <dvyukov@google.com> writes:
> On Fri, Apr 3, 2020 at 3:36 PM OGAWA Hirofumi
> <hirofumi@mail.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@mail.parknet.co.jp>
next prev parent reply other threads:[~2020-04-04 6:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 12:35 KCSAN: data-race in __fat_write_inode / fat12_ent_get syzbot
2020-04-03 13:36 ` OGAWA Hirofumi
2020-04-03 16:36 ` Dmitry Vyukov
2020-04-04 6:14 ` OGAWA Hirofumi [this message]
2020-04-07 10:39 ` Dmitry Vyukov
2020-04-07 13:03 ` OGAWA Hirofumi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dyveq1h.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+6f1624f937d9d6911e2d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).