From: Al Viro <viro@zeniv.linux.org.uk>
To: NeilBrown <neil@brown.name>
Cc: Ian Kent <raven@themaw.net>, Chuck Lever <cel@kernel.org>,
Jake Edge <jake@lwn.net>, Ilya Dryomov <idryomov@gmail.com>,
Alex Markuze <amarkuze@redhat.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
Jan Harkes <jaharkes@cs.cmu.edu>,
coda@cs.cmu.edu, Christian Brauner <brauner@kernel.org>,
Jan Kara <jack@suse.cz>, Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
Amir Goldstein <amir73il@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Miklos Szeredi <mszeredi@redhat.com>,
autofs@vger.kernel.org, linux-kernel@vger.kernel.org,
ceph-devel@vger.kernel.org, codalist@coda.cs.cmu.edu,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH RFC/RFT v2 00/18] Fix easy bits of the negative dentry problem
Date: Sat, 15 Aug 2026 06:03:49 +0100 [thread overview]
Message-ID: <20260815050349.GR2636677@ZenIV> (raw)
In-Reply-To: <20260815042707.2535717-1-neilb@ownmail.net>
On Sat, Aug 15, 2026 at 02:21:17PM +1000, NeilBrown wrote:
> Most of d_walk() already schedules as needed, but I
> think there is still room for improvement, but that can come later.
How the hell could it possibly schedule, when it might very well have
grabbed rename_lock? Confused...
Al, getting through the piles of mail at the moment (sick for a month)...
next prev parent reply other threads:[~2026-08-15 5:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 4:21 [PATCH RFC/RFT v2 00/18] Fix easy bits of the negative dentry problem NeilBrown
2026-08-15 4:21 ` [PATCH v2 01/18] VFS: don't count references through ->d_parent NeilBrown
2026-08-15 4:21 ` [PATCH v2 02/18] autofs: change positive_after() so it takes d_lock rather than the caller NeilBrown
2026-08-15 4:21 ` [PATCH v2 03/18] coda: don't take rcu_read_lock() in coda_flag_children() NeilBrown
2026-08-15 4:21 ` [PATCH v2 04/18] nfs: separate locked regions in nfs_clear_verifier_directory() NeilBrown
2026-08-15 4:21 ` [PATCH v2 05/18] Add and use d_for_each_positive_child family of iterators NeilBrown
2026-08-15 4:21 ` [PATCH v2 06/18] fsnotify: don't hold a spin_lock across fsnotify_recalc_mask() calls NeilBrown
2026-08-15 4:21 ` [PATCH v2 07/18] fsnotify: reduce i_lock hold time in fsnotify_set_children_dentry_flags() NeilBrown
2026-08-15 4:21 ` [PATCH v2 08/18] libfs: simplify scan_positives() NeilBrown
2026-08-15 4:21 ` [PATCH v2 09/18] libfs: change scan_positives() to use d_for_each_positive_child_continue() NeilBrown
2026-08-15 4:21 ` [PATCH v2 10/18] libfs: allow scan_positives() to be called without a cursor NeilBrown
2026-08-15 4:21 ` [PATCH v2 11/18] libfs: replace find_positive_dentry() with scan_positives() NeilBrown
2026-08-15 4:21 ` [PATCH v2 12/18] autofs: don't hold ->lookup_lock in get_next_positive_* NeilBrown
2026-08-15 4:21 ` [PATCH v2 13/18] VFS: don't move dentries in d_sib list when they have the same parent NeilBrown
2026-08-15 4:21 ` [PATCH v2 14/18] Call cond_reshed() as needed in d_for_each_positive_child() NeilBrown
2026-08-15 4:21 ` [PATCH v2 15/18] libfs: remove cond_resched() from scan_positives() NeilBrown
2026-08-15 4:21 ` [PATCH v2 16/18] libfs: rename and export scan_positives() NeilBrown
2026-08-15 4:21 ` [PATCH v2 17/18] autofs: replace positive_after() with d_scan_positives() NeilBrown
2026-08-15 4:21 ` [PATCH v2 18/18] autofs: change get_next_positive_dentry() to NOT accept NULL for start-up NeilBrown
2026-08-15 5:03 ` Al Viro [this message]
2026-08-15 6:12 ` [PATCH RFC/RFT v2 00/18] Fix easy bits of the negative dentry problem NeilBrown
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=20260815050349.GR2636677@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=amarkuze@redhat.com \
--cc=amir73il@gmail.com \
--cc=anna@kernel.org \
--cc=autofs@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=cel@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=idryomov@gmail.com \
--cc=jack@suse.cz \
--cc=jaharkes@cs.cmu.edu \
--cc=jake@lwn.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=neil@brown.name \
--cc=raven@themaw.net \
--cc=slava@dubeyko.com \
--cc=trondmy@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