From: syzbot <syzbot+6b74cf8fcd7378d8be7c@syzkaller.appspotmail.com>
To: feldsherov@google.com, hirofumi@mail.parknet.co.jp, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, tytso@mit.edu,
viro@zeniv.linux.org.uk
Subject: Re: [syzbot] BUG: unable to handle kernel paging request in evict
Date: Tue, 24 Jan 2023 00:57:16 -0800 [thread overview]
Message-ID: <000000000000defd4b05f2feb35c@google.com> (raw)
In-Reply-To: <000000000000e4630c05e974c1eb@google.com>
syzbot suspects this issue was fixed by commit:
commit 4e3c51f4e805291b057d12f5dda5aeb50a538dc4
Author: Svyatoslav Feldsherov <feldsherov@google.com>
Date: Tue Nov 15 20:20:01 2022 +0000
fs: do not update freeing inode i_io_list
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=111208cd480000
start commit: b229b6ca5abb Merge tag 'perf-tools-fixes-for-v6.1-2022-10-..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=1d3548a4365ba17d
dashboard link: https://syzkaller.appspot.com/bug?extid=6b74cf8fcd7378d8be7c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1353a3e2880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16163dce880000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: fs: do not update freeing inode i_io_list
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-24 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 23:36 [syzbot] BUG: unable to handle kernel paging request in evict syzbot
2022-09-25 4:19 ` syzbot
2023-01-24 8:57 ` syzbot [this message]
2023-01-27 7:17 ` Dmitry Vyukov
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=000000000000defd4b05f2feb35c@google.com \
--to=syzbot+6b74cf8fcd7378d8be7c@syzkaller.appspotmail.com \
--cc=feldsherov@google.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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.