From: syzbot <syzbot+21f2b8753d8bfc6bb816@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
miklos@szeredi.hu, nogikh@google.com,
reiserfs-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, willy@infradead.org
Subject: Re: [syzbot] [reiserfs] general protection fault in timerqueue_add (4)
Date: Wed, 12 Jul 2023 04:15:27 -0700 [thread overview]
Message-ID: <000000000000368623060048550c@google.com> (raw)
In-Reply-To: <000000000000d7894b05f5924787@google.com>
syzbot suspects this issue was fixed by commit:
commit d685c668b0695dff927c85e27ef27d4f404f16a3
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Thu Dec 15 21:43:51 2022 +0000
buffer: add b_folio as an alias of b_page
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13d6c9caa80000
start commit: 4a7d37e824f5 Merge tag 'hardening-v6.3-rc1' of git://git.k..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8b969c5af147d31c
dashboard link: https://syzkaller.appspot.com/bug?extid=21f2b8753d8bfc6bb816
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17c64f20c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13734ba0c80000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: buffer: add b_folio as an alias of b_page
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-07-12 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 3:51 [syzbot] [reiserfs?] [fat?] [fuse?] general protection fault in timerqueue_add (4) syzbot
2023-07-12 11:15 ` syzbot [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=000000000000368623060048550c@google.com \
--to=syzbot+21f2b8753d8bfc6bb816@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=nogikh@google.com \
--cc=reiserfs-devel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).