From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
syzbot+1a8e2b31f2ac9bd3d148@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()
Date: Fri, 30 Aug 2024 20:52:00 +0000 [thread overview]
Message-ID: <172505112026.2712133.17685334156318477673.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240730010855.2942132-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 30 Jul 2024 09:08:55 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> __dump_stack lib/dump_stack.c:88 [inline]
> dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
> print_report+0xe8/0x550 mm/kasan/report.c:491
> kasan_report+0x143/0x180 mm/kasan/report.c:601
> kasan_check_range+0x282/0x290 mm/kasan/generic.c:189
> instrument_atomic_read_write include/linux/instrumented.h:96 [inline]
> atomic_fetch_add_relaxed include/linux/atomic/atomic-instrumented.h:252 [inline]
> __refcount_add include/linux/refcount.h:184 [inline]
> __refcount_inc include/linux/refcount.h:241 [inline]
> refcount_inc include/linux/refcount.h:258 [inline]
> get_task_struct include/linux/sched/task.h:118 [inline]
> kthread_stop+0xca/0x630 kernel/kthread.c:704
> f2fs_stop_gc_thread+0x65/0xb0 fs/f2fs/gc.c:210
> f2fs_do_shutdown+0x192/0x540 fs/f2fs/file.c:2283
> f2fs_ioc_shutdown fs/f2fs/file.c:2325 [inline]
> __f2fs_ioctl+0x443a/0xbe60 fs/f2fs/file.c:4325
> vfs_ioctl fs/ioctl.c:51 [inline]
> __do_sys_ioctl fs/ioctl.c:907 [inline]
> __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893
> do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()
https://git.kernel.org/jaegeuk/f2fs/c/c7f114d864ac
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-08-30 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 1:08 Chao Yu
2024-08-30 20:52 ` patchwork-bot+f2fs [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=172505112026.2712133.17685334156318477673.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+1a8e2b31f2ac9bd3d148@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®