From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, hdanton@sina.com,
linux-kernel@vger.kernel.org, Ed.Tsai@mediatek.com,
linux-f2fs-devel@lists.sourceforge.net,
syzbot+763afad57075d3f862f2@syzkaller.appspotmail.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault
Date: Thu, 14 Mar 2024 16:20:31 +0000 [thread overview]
Message-ID: <171043323144.13516.1787617599417094605.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240314020528.3051533-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Thu, 14 Mar 2024 10:05:28 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> BUG: KASAN: slab-use-after-free in f2fs_filemap_fault+0xd1/0x2c0 fs/f2fs/file.c:49
> Read of size 8 at addr ffff88807bb22680 by task syz-executor184/5058
>
> CPU: 0 PID: 5058 Comm: syz-executor184 Not tainted 6.7.0-syzkaller-09928-g052d534373b7 #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
> Call Trace:
> <TASK>
> __dump_stack lib/dump_stack.c:88 [inline]
> dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
> print_address_description mm/kasan/report.c:377 [inline]
> print_report+0x163/0x540 mm/kasan/report.c:488
> kasan_report+0x142/0x170 mm/kasan/report.c:601
> f2fs_filemap_fault+0xd1/0x2c0 fs/f2fs/file.c:49
> __do_fault+0x131/0x450 mm/memory.c:4376
> do_shared_fault mm/memory.c:4798 [inline]
> do_fault mm/memory.c:4872 [inline]
> do_pte_missing mm/memory.c:3745 [inline]
> handle_pte_fault mm/memory.c:5144 [inline]
> __handle_mm_fault+0x23b7/0x72b0 mm/memory.c:5285
> handle_mm_fault+0x27e/0x770 mm/memory.c:5450
> do_user_addr_fault arch/x86/mm/fault.c:1364 [inline]
> handle_page_fault arch/x86/mm/fault.c:1507 [inline]
> exc_page_fault+0x456/0x870 arch/x86/mm/fault.c:1563
> asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault
https://git.kernel.org/jaegeuk/f2fs/c/eb70d5a6c932
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-03-14 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 2:05 [PATCH] f2fs: fix to avoid use-after-free issue in f2fs_filemap_fault Chao Yu
2024-03-14 16:16 ` Jaegeuk Kim
2024-03-14 16:20 ` 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=171043323144.13516.1787617599417094605.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=Ed.Tsai@mediatek.com \
--cc=chao@kernel.org \
--cc=hdanton@sina.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+763afad57075d3f862f2@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