Linux filesystem development
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>,
	Amir Goldstein <amir73il@gmail.com>, Jan Kara <jack@suse.cz>,
	Ian Kent <raven@themaw.net>
Subject: Re: bad things when too many negative dentries in a directory
Date: Sun, 20 Apr 2025 05:49:05 +0100	[thread overview]
Message-ID: <20250420044905.GR2023217@ZenIV> (raw)
In-Reply-To: <CAJfpegs+czRD1=s+o5yNoOp13xH+utQ8jQkJ9ec5283MNT_xmg@mail.gmail.com>

On Fri, Apr 11, 2025 at 11:40:28AM +0200, Miklos Szeredi wrote:

> Except for shrink_dcache_parent() I don't see any uses.  And it's also
> a question whether shrinking negative dentries is useful or not.

One-word answer: umount.

  parent reply	other threads:[~2025-04-20  4:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11  9:40 bad things when too many negative dentries in a directory Miklos Szeredi
2025-04-11 14:47 ` Christian Brauner
2025-04-11 15:40   ` Miklos Szeredi
2025-04-11 16:01     ` Matthew Wilcox
2025-04-14 14:07       ` James Bottomley
2025-04-14 14:30         ` Matthew Wilcox
2025-04-14 15:40           ` James Bottomley
2025-04-14 16:14             ` Matthew Wilcox
2025-04-14 17:58               ` James Bottomley
2025-04-15 17:22                 ` Andreas Dilger
2025-04-16 15:18                   ` Miklos Szeredi
2025-04-16 15:37                     ` Matthew Wilcox
2025-04-16 21:41                     ` Dave Chinner
2025-04-16 15:26                   ` James Bottomley
2025-04-22  6:57                     ` Andreas Dilger
2025-04-14  6:28     ` Ian Kent
2025-04-14  7:17       ` Miklos Szeredi
2025-04-12  1:48   ` Ian Kent
2025-04-12  1:56     ` Ian Kent
2025-04-12  6:31     ` Ian Kent
2025-04-11 21:02 ` Mateusz Guzik
2025-04-20  4:49 ` Al Viro [this message]
2025-05-08 15:45   ` Miklos Szeredi

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=20250420044905.GR2023217@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=raven@themaw.net \
    /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