From: Al Viro <viro@zeniv.linux.org.uk>
To: syzbot <syzbot+84b7b87a6430a152c1f4@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] kernel panic: stack is corrupted in writeback_single_inode
Date: Thu, 29 Sep 2022 21:50:40 +0100 [thread overview]
Message-ID: <YzYFIK/jFiN6WEzT@ZenIV> (raw)
In-Reply-To: <0000000000000f962805e9d6ae62@google.com>
On Thu, Sep 29, 2022 at 01:25:36PM -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: c3e0e1e23c70 Merge tag 'irq_urgent_for_v6.0' of git://git...
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17ab519c880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ba0d23aa7e1ffaf5
> dashboard link: https://syzkaller.appspot.com/bug?extid=84b7b87a6430a152c1f4
> compiler: Debian clang version 13.0.1-++20220126092033+75e33f71c2da-1~exp1~20220126212112.63, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=157c2000880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=105224b8880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/e7f1f925f94e/disk-c3e0e1e2.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/830dabeedf0d/vmlinux-c3e0e1e2.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+84b7b87a6430a152c1f4@syzkaller.appspotmail.com
... and you _still_ have not bothered to Cc ntfs maintainers.
Once more, with feeling:
If you are fuzzing something (ntfs, in this case), the people most
interested in your report are the maintainers of the code in question.
You know that from the moment you put the test together. No matter where
exactly the oops gets triggered, what it looks like, etc.
next prev parent reply other threads:[~2022-09-29 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 4:58 [syzbot] kernel panic: stack is corrupted in writeback_single_inode syzbot
2022-09-28 20:52 ` syzbot
2022-09-29 20:25 ` syzbot
2022-09-29 20:50 ` Al Viro [this message]
2022-09-30 14:09 ` Marco Elver
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=YzYFIK/jFiN6WEzT@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+84b7b87a6430a152c1f4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.