From: Viacheslav Dubeyko <slava@dubeyko.com>
To: torvalds@linux-foundation.org
Cc: linux-nilfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, konishi.ryusuke@gmail.com,
kartikey406@gmail.com, shuangpeng.kernel@gmail.com,
zenghongling@kylinos.cn, Slava.Dubeyko@ibm.com
Subject: [GIT PULL] nilfs2 changes for 7.2-rc1
Date: Mon, 15 Jun 2026 22:54:56 -0700 [thread overview]
Message-ID: <6865b4242f6352ef0b2b40a9cf7a85d12464279e.camel@dubeyko.com> (raw)
Hello Linus,
This pull request contains fixes of syzbot reported issue and
various small fixes in NILFS2 functionality.
Deepanshu Kartikey has fixed syzbot reported issue of a hung
task in nilfs_transaction_begin(). The root cause is that
user-supplied segment numbers are not validated before
nilfs_clean_segments() begins doing work; the range check on
each segnum is performed deep inside the call chain by
nilfs_sufile_updatev(), which emits a nilfs_warn() per invalid entry
while still holding the segctor lock and the sufile mi_sem.
Fix it by validating the contents of kbufs[4] in nilfs_clean_segments()
immediately after acquiring ns_segctor_sem via
nilfs_transaction_lock().
Hongling Zeng has fixed a smatch warning in nilfs_mkdir() warn.
The patch corrects a semantic issue related to the use of the ERR_PTR
macro that arose from a recent VFS change.
Shuangpeng Bai has fixed a backing_dev_info reference leak.
The setup_bdev_super() already initializes sb->s_bdev and takes a
reference on the block device backing_dev_info when assigning sb-
>s_bdi.
nilfs_fill_super() takes another reference to the same
backing_dev_info and stores it in sb->s_bdi again. The extra
reference is not paired with a matching bdi_put(), since
generic_shutdown_super() releases sb->s_bdi only once.
Drop the redundant bdi_get() in nilfs_fill_super(). The single
reference taken by setup_bdev_super() is enough and is released
during superblock shutdown.
The following changes since commit
254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/nilfs2.git
tags/nilfs2-v7.2-tag1
for you to fetch changes up to
e5925f33e4fa9ee313d481557607adce8e30ed2e:
nilfs2: Fix return in nilfs_mkdir (2026-05-20 11:20:56 -0700)
----------------------------------------------------------------
nilfs2 updates for v7.2
- nilfs2: Fix return in nilfs_mkdir
- nilfs2: fix backing_dev_info reference leak
- nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers
----------------------------------------------------------------
Deepanshu Kartikey (1):
nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment
numbers
Hongling Zeng (1):
nilfs2: Fix return in nilfs_mkdir
Shuangpeng Bai (1):
nilfs2: fix backing_dev_info reference leak
fs/nilfs2/namei.c | 2 +-
fs/nilfs2/segment.c | 22 ++++++++++++++++++++++
fs/nilfs2/super.c | 2 --
3 files changed, 23 insertions(+), 3 deletions(-)
next reply other threads:[~2026-06-16 5:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 5:54 Viacheslav Dubeyko [this message]
2026-06-16 7:08 ` 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=6865b4242f6352ef0b2b40a9cf7a85d12464279e.camel@dubeyko.com \
--to=slava@dubeyko.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=kartikey406@gmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nilfs@vger.kernel.org \
--cc=shuangpeng.kernel@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=zenghongling@kylinos.cn \
/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®