public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
	syzbot+74ebe2104433e9dc610d@syzkaller.appspotmail.com,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to cover read extent cache access with lock
Date: Wed, 12 Jun 2024 15:55:57 +0000	[thread overview]
Message-ID: <171820775721.32393.16229302976932686990.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240531020032.1019991-1-chao@kernel.org>

Hello:

This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Fri, 31 May 2024 10:00:32 +0800 you wrote:
> syzbot reports a f2fs bug as below:
> 
> BUG: KASAN: slab-use-after-free in sanity_check_extent_cache+0x370/0x410 fs/f2fs/extent_cache.c:46
> Read of size 4 at addr ffff8880739ab220 by task syz-executor200/5097
> 
> CPU: 0 PID: 5097 Comm: syz-executor200 Not tainted 6.9.0-rc6-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
> Call Trace:
>  <TASK>
>  __dump_stack lib/dump_stack.c:88 [inline]
>  dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114
>  print_address_description mm/kasan/report.c:377 [inline]
>  print_report+0x169/0x550 mm/kasan/report.c:488
>  kasan_report+0x143/0x180 mm/kasan/report.c:601
>  sanity_check_extent_cache+0x370/0x410 fs/f2fs/extent_cache.c:46
>  do_read_inode fs/f2fs/inode.c:509 [inline]
>  f2fs_iget+0x33e1/0x46e0 fs/f2fs/inode.c:560
>  f2fs_nfs_get_inode+0x74/0x100 fs/f2fs/super.c:3237
>  generic_fh_to_dentry+0x9f/0xf0 fs/libfs.c:1413
>  exportfs_decode_fh_raw+0x152/0x5f0 fs/exportfs/expfs.c:444
>  exportfs_decode_fh+0x3c/0x80 fs/exportfs/expfs.c:584
>  do_handle_to_path fs/fhandle.c:155 [inline]
>  handle_to_path fs/fhandle.c:210 [inline]
>  do_handle_open+0x495/0x650 fs/fhandle.c:226
>  do_syscall_x64 arch/x86/entry/common.c:52 [inline]
>  do_syscall_64+0xf5/0x240 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 cover read extent cache access with lock
    https://git.kernel.org/jaegeuk/f2fs/c/d7409b05a64f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2024-06-12 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31  2:00 [PATCH v2] f2fs: fix to cover read extent cache access with lock Chao Yu
2024-06-12 15:55 ` 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=171820775721.32393.16229302976932686990.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+74ebe2104433e9dc610d@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