* [GIT PULL] nilfs2 changes for 7.2-rc1
@ 2026-06-16 5:54 Viacheslav Dubeyko
2026-06-16 7:08 ` pr-tracker-bot
0 siblings, 1 reply; 2+ messages in thread
From: Viacheslav Dubeyko @ 2026-06-16 5:54 UTC (permalink / raw)
To: torvalds
Cc: linux-nilfs, linux-fsdevel, linux-kernel, konishi.ryusuke,
kartikey406, shuangpeng.kernel, zenghongling, Slava.Dubeyko
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(-)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [GIT PULL] nilfs2 changes for 7.2-rc1
2026-06-16 5:54 [GIT PULL] nilfs2 changes for 7.2-rc1 Viacheslav Dubeyko
@ 2026-06-16 7:08 ` pr-tracker-bot
0 siblings, 0 replies; 2+ messages in thread
From: pr-tracker-bot @ 2026-06-16 7:08 UTC (permalink / raw)
To: Viacheslav Dubeyko
Cc: torvalds, linux-nilfs, linux-fsdevel, linux-kernel,
konishi.ryusuke, kartikey406, shuangpeng.kernel, zenghongling,
Slava.Dubeyko
The pull request you sent on Mon, 15 Jun 2026 22:54:56 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/vdubeyko/nilfs2.git tags/nilfs2-v7.2-tag1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6f60a6033c7dfd02ba8d94111965189c9a7866d4
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-06-16 7:08 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-06-16 5:54 [GIT PULL] nilfs2 changes for 7.2-rc1 Viacheslav Dubeyko
2026-06-16 7:08 ` pr-tracker-bot
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®