From: Pavel Skripkin <paskripkin@gmail.com>
To: syzbot <syzbot+c9ff4822a62eee994ea3@syzkaller.appspotmail.com>
Cc: adilger.kernel@dilger.ca, clang-built-linux@googlegroups.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, ndesaulniers@google.com,
syzkaller-bugs@googlegroups.com, tytso@mit.edu
Subject: Re: [syzbot] INFO: task hung in ext4_fill_super
Date: Wed, 16 Jun 2021 19:22:13 +0300 [thread overview]
Message-ID: <20210616192213.1d75d8e2@gmail.com> (raw)
In-Reply-To: <0000000000004c80e405c4df1a2d@google.com>
On Wed, 16 Jun 2021 02:56:21 -0700
syzbot <syzbot+c9ff4822a62eee994ea3@syzkaller.appspotmail.com> wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: f21b807c Merge tag 'drm-fixes-2021-06-11' of
> git://anongit.. git tree: upstream
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=165fca57d00000 kernel
> config: https://syzkaller.appspot.com/x/.config?x=30f476588412c065
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=c9ff4822a62eee994ea3 syz
> repro:
> https://syzkaller.appspot.com/x/repro.syz?x=17d19ce0300000 C
> reproducer: https://syzkaller.appspot.com/x/repro.c?x=108d7988300000
>
> Bisection is inconclusive: the issue happens on the oldest tested
> release.
>
> bisection log:
> https://syzkaller.appspot.com/x/bisect.txt?x=1646b8d0300000 final
> oops: https://syzkaller.appspot.com/x/report.txt?x=1546b8d0300000
> console output:
> https://syzkaller.appspot.com/x/log.txt?x=1146b8d0300000
>
> IMPORTANT: if you fix the issue, please add the following tag to the
> commit: Reported-by:
> syzbot+c9ff4822a62eee994ea3@syzkaller.appspotmail.com
>
Just want to try this ;)
#syz test https://linux.googlesource.com/linux/kernel/git/torvalds/linux refs/changes/76/10176/6
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2021-06-16 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 9:56 [syzbot] INFO: task hung in ext4_fill_super syzbot
2021-06-16 16:22 ` Pavel Skripkin [this message]
2021-06-16 18:28 ` syzbot
2021-08-05 14:26 ` Pavel Skripkin
2021-08-05 14:46 ` syzbot
2021-08-06 7:45 ` Pavel Skripkin
2021-08-06 10:14 ` syzbot
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=20210616192213.1d75d8e2@gmail.com \
--to=paskripkin@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=syzbot+c9ff4822a62eee994ea3@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
/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).