From: syzbot <syzbot+3a36aeabd31497d63f6e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [syzbot] [gfs2?] KASAN: slab-use-after-free Read in gfs2_invalidate_folio
Date: Sun, 14 Apr 2024 18:13:44 -0700 [thread overview]
Message-ID: <00000000000032618c06161855cf@google.com> (raw)
In-Reply-To: <0000000000004f557c0615d47e6d@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [syzbot] [gfs2?] KASAN: slab-use-after-free Read in gfs2_invalidate_folio
Author: lizhi.xu@windriver.com
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git e8c39d0f57f3
diff --git a/fs/gfs2/log.c b/fs/gfs2/log.c
index 8cddf955ebc0..71ce8d1576cc 100644
--- a/fs/gfs2/log.c
+++ b/fs/gfs2/log.c
@@ -1007,6 +1007,7 @@ static void trans_drain(struct gfs2_trans *tr)
{
struct gfs2_bufdata *bd;
struct list_head *head;
+ struct buffer_head *bh;
if (!tr)
return;
@@ -1022,6 +1023,8 @@ static void trans_drain(struct gfs2_trans *tr)
head = &tr->tr_databuf;
while (!list_empty(head)) {
bd = list_first_entry(head, struct gfs2_bufdata, bd_list);
+ bh = bd->bd_bh;
+ bh->b_private = NULL;
list_del_init(&bd->bd_list);
if (!list_empty(&bd->bd_ail_st_list))
gfs2_remove_from_ail(bd);
next prev parent reply other threads:[~2024-04-15 1:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 16:17 [syzbot] [gfs2?] KASAN: slab-use-after-free Read in gfs2_invalidate_folio syzbot
2024-04-13 5:41 ` Edward Adam Davis
2024-04-13 5:54 ` syzbot
2024-04-13 9:19 ` Edward Adam Davis
2024-04-13 9:36 ` syzbot
2024-04-13 14:48 ` Edward Adam Davis
2024-04-13 15:05 ` syzbot
2024-04-14 1:48 ` Edward Adam Davis
2024-04-14 2:04 ` syzbot
2024-04-14 8:56 ` Edward Adam Davis
2024-04-14 9:13 ` syzbot
2024-04-15 1:13 ` syzbot [this message]
2024-04-15 2:04 ` [syzbot] " syzbot
2025-06-05 14:20 ` [syzbot] #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git ec7714e4947909190ffb3041a03311a975350fe0 syzbot
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=00000000000032618c06161855cf@google.com \
--to=syzbot+3a36aeabd31497d63f6e@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).