mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Christian Brauner <brauner@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Tejun Heo <tj@kernel.org>, Shakeel Butt <shakeel.butt@linux.dev>
Cc: Meta kernel team <kernel-team@meta.com>,
	driver-core@lists.linux.dev, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] kernfs: remove kernfs_rwsem from dentry revalidation
Date: Wed, 26 Aug 2026 12:02:57 +0800	[thread overview]
Message-ID: <1c96890d-5ec9-4f2d-a897-8f8c46ea87f7@themaw.net> (raw)
In-Reply-To: <20260825-grabmal-erwachen-aufatmen-b62c5d6c220e@brauner>

On 25/8/26 22:58, Christian Brauner wrote:
> On Thu, 20 Aug 2026 22:05:03 -0700, Shakeel Butt wrote:
>> kernfs: remove kernfs_rwsem from dentry revalidation
>>
>> At Meta, we are seeing important system daemons that poll cgroupfs and
>> sysfs geth stuck in kernfs_dop_revalidate() for minutes. The two that
>> hurt most are the ones we can least afford to lose: oomd, which decides
>> what to kill when a machine runs out of memory, and below[1], which
>> records the telemetry used to understand what happened afterwards.
>>
>> [...]
> Applied to the vfs-7.4.kernfs branch of the vfs/vfs.git tree.
> Patches in the vfs-7.4.kernfs 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.


I have a report against kernfs where I cannot find a reason for significant

contention, primarily on ->revaliate(), in either of two vmcores, exactly

the case described in this series.


I reviewed the series and it looks good to me.

The descriptions justifying the changes also look sound.


While I think renames and removals should be ok based on the descriptions

justifying the change (my biggest concern with removing the rwsem) I'll

continue to ponder its implications for a while.


Reviewed-by: Ian Kent <raven@themaw.net>


>
> 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: vfs-7.4.kernfs
>
> [1/4] kernfs: Use VFS lookup context in d_revalidate()
>        https://git.kernel.org/vfs/vfs/c/b3c97f5cb084
> [2/4] kernfs: Prepare directory revisions for lockless reads
>        https://git.kernel.org/vfs/vfs/c/272e0997df44
> [3/4] kernfs: Avoid namespace dereference in d_revalidate()
>        https://git.kernel.org/vfs/vfs/c/e1c629a8dbc7
> [4/4] kernfs: Remove kernfs_rwsem from dentry revalidation
>        https://git.kernel.org/vfs/vfs/c/8c6ad578e2f0
>
>

      reply	other threads:[~2026-08-26  4:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  5:05 Shakeel Butt
2026-08-21  5:05 ` [PATCH 1/4] kernfs: Use VFS lookup context in d_revalidate() Shakeel Butt
2026-08-21  5:05 ` [PATCH 2/4] kernfs: Prepare directory revisions for lockless reads Shakeel Butt
2026-08-21  5:05 ` [PATCH 3/4] kernfs: Avoid namespace dereference in d_revalidate() Shakeel Butt
2026-08-21  5:05 ` [PATCH 4/4] kernfs: Remove kernfs_rwsem from dentry revalidation Shakeel Butt
2026-09-11 18:33   ` Sandeep Dhavale
2026-09-11 19:31     ` Shakeel Butt
2026-09-11 21:11       ` Sandeep Dhavale
2026-09-12  3:09         ` Shakeel Butt
2026-09-12  3:28           ` Sandeep Dhavale
2026-09-15  2:33             ` Ian Kent
2026-08-25 14:58 ` [PATCH 0/4] kernfs: remove " Christian Brauner
2026-08-26  4:02   ` Ian Kent [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=1c96890d-5ec9-4f2d-a897-8f8c46ea87f7@themaw.net \
    --to=raven@themaw.net \
    --cc=brauner@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=tj@kernel.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 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®