From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] f2fs fix for 6.18-rc2
Date: Thu, 16 Oct 2025 17:39:39 +0000 [thread overview]
Message-ID: <aPEt2-u8J16L9Xnk@google.com> (raw)
Hi Linus,
Could you please consider this pull request?
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-fix-6.18-rc2
for you to fetch changes up to 9d5c4f5c7a2c7677e1b3942772122b032c265aae:
f2fs: fix wrong block mapping for multi-devices (2025-10-13 23:55:44 +0000)
----------------------------------------------------------------
f2fs-fix-6.18-rc2
This includes two urgent fixes:
1) iput() added by bc986b1d756482a causes soft lockup [1].
2) fix a wrong block address map on multiple devices.
[1] https://lore.kernel.org/oe-lkp/202509301450.138b448f-lkp@intel.com
----------------------------------------------------------------
Jaegeuk Kim (1):
f2fs: fix wrong block mapping for multi-devices
Mateusz Guzik (1):
f2fs: don't call iput() from f2fs_drop_inode()
fs/f2fs/data.c | 2 +-
fs/f2fs/super.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
Thanks,
next reply other threads:[~2025-10-16 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 17:39 Jaegeuk Kim [this message]
2025-10-16 18:06 ` [f2fs-dev] [GIT PULL] f2fs fix for 6.18-rc2 pr-tracker-bot
2025-10-16 18:24 ` patchwork-bot+f2fs
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=aPEt2-u8J16L9Xnk@google.com \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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