From: Ryusuke Konishi <konishi.ryusuke@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-nilfs <linux-nilfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] nilfs2 fixes on v6.19-rc1
Date: Sat, 20 Dec 2025 03:04:24 +0900 [thread overview]
Message-ID: <20251219180631.27554-1-konishi.ryusuke@gmail.com> (raw)
Hi Viacheslav,
I'm submitting three nilfs2 fixes as a patch series (rather than a
pull request as previously mentioned), so please queue them in your
tree.
Two of the three involve kernel-doc issues in uapi header files. These
are suitable for the next cycle.
The remaining one, which I'm sure you've seen, fixes an issue recently
reported by syzbot involving the FITRIM ioctl, and is a slightly
higher priority.
If possible, I'd like you to submit this as a bugfix patch without
waiting for the next release cycle, but if you're limiting your pull
requests to merge windows, feel free to submit it together with ones
for v6.20-rc1 at your convenience.
Thanks,
Ryusuke Konishi
Edward Adam Davis (1):
nilfs2: Fix potential block overflow that cause system hang
Randy Dunlap (1):
nilfs2: convert nilfs_super_block to kernel-doc
Ryusuke Konishi (1):
nilfs2: fix missing struct keywords in nilfs2_api.h kernel-doc
fs/nilfs2/sufile.c | 4 +
include/uapi/linux/nilfs2_api.h | 4 +-
include/uapi/linux/nilfs2_ondisk.h | 163 +++++++++++++++++------------
3 files changed, 103 insertions(+), 68 deletions(-)
--
2.43.0
next reply other threads:[~2025-12-19 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 18:04 Ryusuke Konishi [this message]
2025-12-19 18:04 ` [PATCH 1/3] nilfs2: Fix potential block overflow that cause system hang Ryusuke Konishi
2025-12-19 18:04 ` [PATCH 2/3] nilfs2: convert nilfs_super_block to kernel-doc Ryusuke Konishi
2025-12-19 18:04 ` [PATCH 3/3] nilfs2: fix missing struct keywords in nilfs2_api.h kernel-doc Ryusuke Konishi
2025-12-23 0:16 ` [PATCH 0/3] nilfs2 fixes on v6.19-rc1 Viacheslav Dubeyko
2025-12-23 3:32 ` Ryusuke Konishi
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=20251219180631.27554-1-konishi.ryusuke@gmail.com \
--to=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=slava@dubeyko.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