From: syzbot <syzbot+5b129e8586277719bab3@syzkaller.appspotmail.com>
To: dhowells@redhat.com, dvyukov@google.com,
linux-cachefs-bounces@redhat.com, linux-cachefs-owner@redhat.com,
linux-cachefs@redhat.com, linux-kernel@vger.kernel.org,
mudongliangabcd@gmail.com, nogikh@google.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in fscache_free_cookie
Date: Thu, 20 Oct 2022 00:36:31 -0700 [thread overview]
Message-ID: <0000000000004ab16105eb726264@google.com> (raw)
In-Reply-To: <000000000000f2b07b05d5dc87cc@google.com>
This bug is marked as fixed by commit:
fscache: fix GPF in fscache_free_cookie
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new crashes with the same signature are ignored.
next prev parent reply other threads:[~2022-10-20 7:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 15:00 [syzbot] general protection fault in fscache_free_cookie syzbot
2022-04-20 9:14 ` syzbot
2022-05-04 9:15 ` syzbot
2022-05-18 9:15 ` syzbot
2022-06-01 9:16 ` syzbot
2022-06-15 9:17 ` syzbot
2022-06-29 9:18 ` syzbot
2022-07-13 9:19 ` syzbot
2022-07-27 9:20 ` syzbot
2022-08-10 9:21 ` syzbot
2022-08-24 9:22 ` syzbot
2022-08-24 12:23 ` David Howells
2022-08-31 9:13 ` Aleksandr Nogikh
2022-09-14 9:14 ` syzbot
2022-09-28 9:15 ` syzbot
2022-09-28 9:21 ` Dongliang Mu
2022-10-06 7:35 ` Dmitry Vyukov
2022-10-20 7:36 ` syzbot [this message]
2022-11-03 7:37 ` syzbot
2022-11-17 7:38 ` syzbot
2022-12-01 7:39 ` syzbot
2022-12-15 7:40 ` syzbot
2022-12-29 7:41 ` syzbot
2023-01-12 7:42 ` syzbot
2023-01-26 7:43 ` syzbot
2023-02-09 7:44 ` syzbot
2023-02-09 9:03 ` 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=0000000000004ab16105eb726264@google.com \
--to=syzbot+5b129e8586277719bab3@syzkaller.appspotmail.com \
--cc=dhowells@redhat.com \
--cc=dvyukov@google.com \
--cc=linux-cachefs-bounces@redhat.com \
--cc=linux-cachefs-owner@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mudongliangabcd@gmail.com \
--cc=nogikh@google.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.