public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Mateusz Guzik <mjguzik@gmail.com>,
	brauner@kernel.org, viro@zeniv.linux.org.uk, jack@suse.cz,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/2] fs: cache the string generated by reading /proc/filesystems
Date: Fri, 4 Apr 2025 01:41:27 -0700	[thread overview]
Message-ID: <Z--bN3WetGcsQmnx@infradead.org> (raw)
In-Reply-To: <87h63bpnib.fsf@igel.home>

On Sat, Mar 29, 2025 at 09:53:16PM +0100, Andreas Schwab wrote:
> On Mär 29 2025, Mateusz Guzik wrote:
> 
> > It is being read surprisingly often (e.g., by mkdir, ls and even sed!).
> 
> It is part of libselinux (selinuxfs_exits), called by its library
> initializer.

Can we please fix libselinux instead of working around this really
broken behavior in the kernel?


  reply	other threads:[~2025-04-04  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-29 19:28 [PATCH 0/2] speed up /proc/filesystems Mateusz Guzik
2025-03-29 19:28 ` [PATCH 1/2] proc: add a helper for marking files as permanent by external consumers Mateusz Guzik
2025-03-29 19:28 ` [PATCH 2/2] fs: cache the string generated by reading /proc/filesystems Mateusz Guzik
2025-03-29 20:53   ` Andreas Schwab
2025-04-04  8:41     ` Christoph Hellwig [this message]
2025-04-05  4:55       ` Mateusz Guzik
2025-04-05  5:26         ` Mateusz Guzik
2025-04-01 10:30   ` Christian Brauner
2025-04-01 12:12     ` Mateusz Guzik
2025-04-01 10:34 ` [PATCH 0/2] speed up /proc/filesystems Christian Brauner

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=Z--bN3WetGcsQmnx@infradead.org \
    --to=hch@infradead.org \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjguzik@gmail.com \
    --cc=schwab@linux-m68k.org \
    --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