From: Jaegeuk Kim via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [f2fs-dev] [GIT PULL] f2fs fixes for 6.16-rc4
Date: Mon, 23 Jun 2025 18:12:59 +0000 [thread overview]
Message-ID: <aFmZKyrDBDzTzs4Q@google.com> (raw)
Hi Linus,
Could you please help mergint this bug fix series?
Thanks,
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-6.16-rc4
for you to fetch changes up to ba8dac350faf16afc129ce6303ca4feaf083ccb1:
f2fs: fix to zero post-eof page (2025-06-18 21:35:29 +0000)
----------------------------------------------------------------
f2fs-for-6.16-rc4
There are two bug fixes: 1) double-unlock introduced by the recent folio
conversion, 2) stale page content beyond eof complained by xfstests/generic/363.
----------------------------------------------------------------
Chao Yu (1):
f2fs: fix to zero post-eof page
Matthew Wilcox (Oracle) (1):
f2fs: Fix __write_node_folio() conversion
fs/f2fs/file.c | 38 ++++++++++++++++++++++++++++++++++++++
fs/f2fs/node.c | 1 -
2 files changed, 38 insertions(+), 1 deletion(-)
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux F2FS Dev Mailing List
<linux-f2fs-devel@lists.sourceforge.net>
Subject: [GIT PULL] f2fs fixes for 6.16-rc4
Date: Mon, 23 Jun 2025 18:12:59 +0000 [thread overview]
Message-ID: <aFmZKyrDBDzTzs4Q@google.com> (raw)
Hi Linus,
Could you please help mergint this bug fix series?
Thanks,
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-6.16-rc4
for you to fetch changes up to ba8dac350faf16afc129ce6303ca4feaf083ccb1:
f2fs: fix to zero post-eof page (2025-06-18 21:35:29 +0000)
----------------------------------------------------------------
f2fs-for-6.16-rc4
There are two bug fixes: 1) double-unlock introduced by the recent folio
conversion, 2) stale page content beyond eof complained by xfstests/generic/363.
----------------------------------------------------------------
Chao Yu (1):
f2fs: fix to zero post-eof page
Matthew Wilcox (Oracle) (1):
f2fs: Fix __write_node_folio() conversion
fs/f2fs/file.c | 38 ++++++++++++++++++++++++++++++++++++++
fs/f2fs/node.c | 1 -
2 files changed, 38 insertions(+), 1 deletion(-)
next reply other threads:[~2025-06-23 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 18:12 Jaegeuk Kim via Linux-f2fs-devel [this message]
2025-06-23 18:12 ` [GIT PULL] f2fs fixes for 6.16-rc4 Jaegeuk Kim
2025-06-23 22:10 ` [f2fs-dev] " pr-tracker-bot--- via Linux-f2fs-devel
2025-06-23 22:10 ` pr-tracker-bot
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=aFmZKyrDBDzTzs4Q@google.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.