All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cae7809e9dc1459e4e63@syzkaller.appspotmail.com>
To: dxdt@dev.snart.me, linux-f2fs-devel@lists.sourceforge.net,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [mm?] [exfat?] [f2fs?] memory leak in __kfree_rcu_sheaf
Date: Mon, 04 May 2026 13:51:01 -0700	[thread overview]
Message-ID: <69f906b5.050a0220.892e9.00d7.GAE@google.com> (raw)
In-Reply-To: <2956b248-c79f-4eae-8bfc-81178b5899af@dev.snart.me>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel panic: !!! sbi at ADDR used after freeing !!!

F2FS-fs (loop1): f2fs_record_error_work()
Kernel panic - not syncing: !!! sbi at ffff888129322000 used after freeing !!!
CPU: 1 UID: 0 PID: 6598 Comm: kworker/1:5 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: events f2fs_record_error_work
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x97/0xe0 lib/dump_stack.c:120
 vpanic+0x383/0x6d0 kernel/panic.c:650
 panic+0x6e/0x70 kernel/panic.c:787
 f2fs_record_error_work.cold+0x14/0x14 fs/f2fs/super.c:4747
 process_one_work+0x277/0x5b0 kernel/workqueue.c:3302
 process_scheduled_works kernel/workqueue.c:3385 [inline]
 worker_thread+0x255/0x4a0 kernel/workqueue.c:3466
 kthread+0x14e/0x1a0 kernel/kthread.c:436
 ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Kernel Offset: disabled


Tested on:

commit:         6d35786d Merge tag 'for-linus' of git://git.kernel.org..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a63a36580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9645c21cfd1d3e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=cae7809e9dc1459e4e63
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch:          https://syzkaller.appspot.com/x/patch.diff?x=172b8ad2580000



_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+cae7809e9dc1459e4e63@syzkaller.appspotmail.com>
To: dxdt@dev.snart.me, linux-f2fs-devel@lists.sourceforge.net,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [exfat?] [f2fs?] memory leak in __kfree_rcu_sheaf
Date: Mon, 04 May 2026 13:51:01 -0700	[thread overview]
Message-ID: <69f906b5.050a0220.892e9.00d7.GAE@google.com> (raw)
In-Reply-To: <2956b248-c79f-4eae-8bfc-81178b5899af@dev.snart.me>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
kernel panic: !!! sbi at ADDR used after freeing !!!

F2FS-fs (loop1): f2fs_record_error_work()
Kernel panic - not syncing: !!! sbi at ffff888129322000 used after freeing !!!
CPU: 1 UID: 0 PID: 6598 Comm: kworker/1:5 Not tainted syzkaller #0 PREEMPT(full) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
Workqueue: events f2fs_record_error_work
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x97/0xe0 lib/dump_stack.c:120
 vpanic+0x383/0x6d0 kernel/panic.c:650
 panic+0x6e/0x70 kernel/panic.c:787
 f2fs_record_error_work.cold+0x14/0x14 fs/f2fs/super.c:4747
 process_one_work+0x277/0x5b0 kernel/workqueue.c:3302
 process_scheduled_works kernel/workqueue.c:3385 [inline]
 worker_thread+0x255/0x4a0 kernel/workqueue.c:3466
 kthread+0x14e/0x1a0 kernel/kthread.c:436
 ret_from_fork+0x219/0x490 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Kernel Offset: disabled


Tested on:

commit:         6d35786d Merge tag 'for-linus' of git://git.kernel.org..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17a63a36580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9645c21cfd1d3e8f
dashboard link: https://syzkaller.appspot.com/bug?extid=cae7809e9dc1459e4e63
compiler:       gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch:          https://syzkaller.appspot.com/x/patch.diff?x=172b8ad2580000


  reply	other threads:[~2026-05-04 20:51 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09 18:26 [f2fs-dev] [syzbot] [mm?] [f2fs?] [exfat?] memory leak in __kfree_rcu_sheaf syzbot
2026-02-09 18:26 ` syzbot
2026-03-02  3:41 ` [f2fs-dev] " Qing Wang
2026-03-02  3:41   ` Qing Wang
2026-03-02  3:57   ` [f2fs-dev] " syzbot
2026-03-02  3:57     ` syzbot
2026-03-02  8:39   ` [f2fs-dev] " Vlastimil Babka (SUSE) via Linux-f2fs-devel
2026-03-02  8:39     ` Vlastimil Babka (SUSE)
2026-03-04  1:30     ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-04  1:30       ` Harry Yoo
2026-03-04 13:39       ` [f2fs-dev] " Vlastimil Babka (SUSE) via Linux-f2fs-devel
2026-03-04 13:39         ` Vlastimil Babka (SUSE)
2026-03-06 19:35         ` [f2fs-dev] " Catalin Marinas
2026-03-06 19:35           ` Catalin Marinas
2026-03-08 11:02           ` [f2fs-dev] " Catalin Marinas
2026-03-08 11:02             ` Catalin Marinas
2026-03-08 12:31             ` [f2fs-dev] " syzbot
2026-03-08 12:31               ` syzbot
2026-03-08 11:04           ` [f2fs-dev] " Catalin Marinas
2026-03-08 11:04             ` Catalin Marinas
2026-03-08 12:42             ` [f2fs-dev] " syzbot
2026-03-08 12:42               ` syzbot
2026-03-09 10:46           ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-09 10:46             ` Harry Yoo
2026-03-09 11:11             ` [f2fs-dev] " syzbot
2026-03-09 11:11               ` syzbot
2026-03-09 12:17           ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-09 12:17             ` Harry Yoo
2026-03-09 20:31             ` [f2fs-dev] " Catalin Marinas
2026-03-09 20:31               ` Catalin Marinas
2026-03-11  3:04               ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-11  3:04                 ` Harry Yoo
2026-03-11  3:20                 ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-11  3:20                   ` Harry Yoo
2026-03-10  3:39           ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-10  3:39             ` Harry Yoo
2026-03-10  3:54             ` [f2fs-dev] " syzbot
2026-03-10  3:54               ` syzbot
2026-03-10  6:11               ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-10  6:11                 ` Harry Yoo
2026-03-10  6:29                 ` [f2fs-dev] " syzbot
2026-03-10  6:29                   ` syzbot
2026-03-10  8:10                   ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-10  8:10                     ` Harry Yoo
2026-03-10  9:40                     ` [f2fs-dev] " syzbot
2026-03-10  9:40                       ` syzbot
2026-03-18  2:34                     ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-18  2:34                       ` Harry Yoo
2026-03-18  3:08                       ` [f2fs-dev] " syzbot
2026-03-18  3:08                         ` syzbot
2026-03-18  4:10                     ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-18  4:10                       ` Harry Yoo
2026-03-18  5:02                       ` [f2fs-dev] " syzbot
2026-03-18  5:02                         ` syzbot
2026-03-11  9:57 ` [f2fs-dev] " Qing Wang
2026-03-11  9:57   ` Qing Wang
2026-03-11 10:17   ` [f2fs-dev] " syzbot
2026-03-11 10:17     ` syzbot
2026-03-11 10:48 ` [f2fs-dev] " Qing Wang
2026-03-11 10:48   ` Qing Wang
2026-03-11 11:03   ` [f2fs-dev] " syzbot
2026-03-11 11:03     ` syzbot
2026-03-11 11:23   ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-11 11:23     ` Harry Yoo
2026-03-20  0:06 ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-20  0:06   ` Harry Yoo
2026-03-20 10:34   ` [f2fs-dev] " syzbot
2026-03-20 10:34     ` syzbot
2026-03-20 11:20 ` [f2fs-dev] " Harry Yoo via Linux-f2fs-devel
2026-03-20 11:20   ` Harry Yoo
2026-05-02 10:09 ` David Timber
2026-05-03  6:00 ` David Timber
2026-05-03  7:17   ` [f2fs-dev] [syzbot] [mm?] [exfat?] [f2fs?] " syzbot
2026-05-03  7:17     ` syzbot
2026-05-03  6:05 ` [syzbot] [mm?] [f2fs?] [exfat?] " David Timber
2026-05-03  7:27   ` [f2fs-dev] [syzbot] [mm?] [exfat?] [f2fs?] " syzbot
2026-05-03  7:27     ` syzbot
2026-05-03  7:41     ` [f2fs-dev] " David Timber via Linux-f2fs-devel
2026-05-03  7:41       ` David Timber
2026-05-04 20:17 ` [syzbot] [mm?] [f2fs?] [exfat?] " David Timber
2026-05-04 20:51   ` syzbot [this message]
2026-05-04 20:51     ` [syzbot] [mm?] [exfat?] [f2fs?] " syzbot
2026-05-04 20:26 ` [syzbot] [mm?] [f2fs?] [exfat?] " David Timber
2026-05-04 21:12   ` [f2fs-dev] [syzbot] [mm?] [exfat?] [f2fs?] " syzbot
2026-05-04 21:12     ` 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=69f906b5.050a0220.892e9.00d7.GAE@google.com \
    --to=syzbot+cae7809e9dc1459e4e63@syzkaller.appspotmail.com \
    --cc=dxdt@dev.snart.me \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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.