From: Marco Elver <elver@google.com>
To: syzbot <syzbot+9d90dad32dd9727ed084@syzkaller.appspotmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: [syzbot] KFENCE: use-after-free in kmem_cache_destroy
Date: Tue, 18 May 2021 16:47:25 +0200 [thread overview]
Message-ID: <YKPTfbqFcWijSB46@elver.google.com> (raw)
In-Reply-To: <CANpmjNOXXt6HAYw9k-hwZvquTQW58hpbN4yzuujbwOuD3Q2p4g@mail.gmail.com>
[-Cc most to avoid spam]
> > https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=dev&id=cad83c968c2ebe97905f900326988ed37146c347
>
> Ah, nice, thank you!
> I wasn't sure if there had already been a fix, so I just wanted to follow up.
Let's try again without the line break that GMail introduces...
#syz fix: f2fs: fix to avoid racing on fsync_entry_slab by multi filesystem instances
prev parent reply other threads:[~2021-05-18 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 8:24 [syzbot] KFENCE: use-after-free in kmem_cache_destroy syzbot
2021-05-03 8:27 ` Dmitry Vyukov
2021-05-18 11:14 ` Marco Elver
2021-05-18 14:26 ` Chao Yu
2021-05-18 14:41 ` Marco Elver
2021-05-18 14:47 ` Marco Elver [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=YKPTfbqFcWijSB46@elver.google.com \
--to=elver@google.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9d90dad32dd9727ed084@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox