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>,
syzkaller <syzkaller@googlegroups.com>
Subject: Re: KCSAN: data-race in __fat_write_inode / fat12_ent_get
Date: Tue, 07 Apr 2020 22:03:16 +0900 [thread overview]
Message-ID: <874ktva1nv.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <CACT4Y+ZQ4Uw7uP36ULiAQ_MSB8KkXhBSZhWTXZaMybn2acK1Sg@mail.gmail.com> (Dmitry Vyukov's message of "Tue, 7 Apr 2020 12:39:28 +0200")
Dmitry Vyukov <dvyukov@google.com> writes:
>> 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.
>
>
> I've converted the program to C using syz-prog2c:
> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#syzkaller-reproducers
> then slightly changed the generated program to dump the file to disk
> rather than mounting.
>
> The resulting image is attached (archived because it's mostly zeros).
Thank you! I think I can see now why the generated image became the
cause of this.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2020-04-07 13:03 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
2020-04-07 10:39 ` Dmitry Vyukov
2020-04-07 13:03 ` OGAWA Hirofumi [this message]
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=874ktva1nv.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 \
--cc=syzkaller@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