From: Christian Brauner <brauner@kernel.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
viro@zeniv.linux.org.uk, jack@suse.cz,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] assorted ->i_count changes + extension of lockless handling
Date: Wed, 22 Apr 2026 15:02:00 +0200 [thread overview]
Message-ID: <20260422-wortgefecht-tummeln-e95204f0437e@brauner> (raw)
In-Reply-To: <20260421182538.1215894-1-mjguzik@gmail.com>
On Tue, 21 Apr 2026 20:25:35 +0200, Mateusz Guzik wrote:
> The stock kernel support partial lockless in handling in that iput() can
> decrement any value > 1. Any ref acquire however requires the spinlock.
>
> With this patchset ref acquires when the value was already at least 1
> also become lockless. That is, only transitions 0->1 and 1->0 take the
> lock.
>
> [...]
Applied to the vfs-7.2.inode branch of the vfs/vfs.git tree.
Patches in the vfs-7.2.inode branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: master
[1/3] fs: add icount_read_once() and stop open-coding ->i_count loads
https://git.kernel.org/vfs/vfs/c/11abd8ebfe89
[2/3] fs: relocate and tidy up ihold()
https://git.kernel.org/vfs/vfs/c/f16fbfa2a006
[3/3] fs: allow lockless ->i_count bumps as long as it does not transition 0->1
https://git.kernel.org/vfs/vfs/c/e22934526e6d
prev parent reply other threads:[~2026-04-22 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 18:25 [PATCH v6 0/3] assorted ->i_count changes + extension of lockless handling Mateusz Guzik
2026-04-21 18:25 ` [PATCH v6 1/3] fs: add icount_read_once() and stop open-coding ->i_count loads Mateusz Guzik
2026-04-22 10:17 ` Jan Kara
2026-04-21 18:25 ` [PATCH v6 2/3] fs: relocate and tidy up ihold() Mateusz Guzik
2026-04-22 10:18 ` Jan Kara
2026-04-21 18:25 ` [PATCH v6 3/3] fs: allow lockless ->i_count bumps as long as it does not transition 0->1 Mateusz Guzik
2026-04-22 10:26 ` Jan Kara
2026-04-22 13:02 ` Christian Brauner [this message]
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=20260422-wortgefecht-tummeln-e95204f0437e@brauner \
--to=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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