mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, r772577952@gmail.com, stable@kernel.org,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to avoid out-of-boundary access in dnode page
Date: Fri, 18 Jul 2025 20:20:04 +0000	[thread overview]
Message-ID: <175287000476.2782346.18225378290339645502.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250717132633.1339965-1-chao@kernel.org>

Hello:

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

On Thu, 17 Jul 2025 21:26:33 +0800 you wrote:
> As Jiaming Zhang reported:
> 
>  <TASK>
>  __dump_stack lib/dump_stack.c:94 [inline]
>  dump_stack_lvl+0x1c1/0x2a0 lib/dump_stack.c:120
>  print_address_description mm/kasan/report.c:378 [inline]
>  print_report+0x17e/0x800 mm/kasan/report.c:480
>  kasan_report+0x147/0x180 mm/kasan/report.c:593
>  data_blkaddr fs/f2fs/f2fs.h:3053 [inline]
>  f2fs_data_blkaddr fs/f2fs/f2fs.h:3058 [inline]
>  f2fs_get_dnode_of_data+0x1a09/0x1c40 fs/f2fs/node.c:855
>  f2fs_reserve_block+0x53/0x310 fs/f2fs/data.c:1195
>  prepare_write_begin fs/f2fs/data.c:3395 [inline]
>  f2fs_write_begin+0xf39/0x2190 fs/f2fs/data.c:3594
>  generic_perform_write+0x2c7/0x910 mm/filemap.c:4112
>  f2fs_buffered_write_iter fs/f2fs/file.c:4988 [inline]
>  f2fs_file_write_iter+0x1ec8/0x2410 fs/f2fs/file.c:5216
>  new_sync_write fs/read_write.c:593 [inline]
>  vfs_write+0x546/0xa90 fs/read_write.c:686
>  ksys_write+0x149/0x250 fs/read_write.c:738
>  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
>  do_syscall_64+0xf3/0x3d0 arch/x86/entry/syscall_64.c:94
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> 
> [...]

Here is the summary with links:
  - [f2fs-dev] f2fs: fix to avoid out-of-boundary access in dnode page
    https://git.kernel.org/jaegeuk/f2fs/c/026e81230291

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



      reply	other threads:[~2025-07-18 20:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-17 13:26 Chao Yu
2025-07-18 20: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=175287000476.2782346.18225378290339645502.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=r772577952@gmail.com \
    --cc=stable@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

all inboxes | Powered by JetHome®