->d_revalidate() calling conventions changes (->d_parent/->d_name stability problems)
From: | Al Viro <viro-AT-zeniv.linux.org.uk> | |
To: | linux-fsdevel-AT-vger.kernel.org | |
Subject: | [PATCHES v2][RFC][CFT] ->d_revalidate() calling conventions changes (->d_parent/->d_name stability problems) | |
Date: | Thu, 16 Jan 2025 05:21:03 +0000 | |
Message-ID: | <20250116052103.GF1977892@ZenIV> | |
Cc: | Linus Torvalds <torvalds-AT-linux-foundation.org>, Gabriel Krisman Bertazi <krisman-AT-kernel.org>, Christian Brauner <brauner-AT-kernel.org>, Jan Kara <jack-AT-suse.cz>, David Howells <dhowells-AT-redhat.com>, ceph-devel-AT-vger.kernel.org, linux-nfs-AT-vger.kernel.org, Amir Goldstein <amir73il-AT-gmail.com>, Miklos Szeredi <miklos-AT-szeredi.hu>, Andreas Gruenbacher <agruenba-AT-redhat.com>, Mike Marshall <hubcap-AT-omnibond.com> | |
Archive-link: | Article |
Series updated and force-pushed to the same place: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git #work.d_revalidate itself on top of #work.dcache. Individual patches in followups; please, review. Changes since v1: * reordered external_name members to get rid of hole on 64bit, as suggested by dhowells. * split the added method in two in the last commit ("9p: fix ->rename_sem exclusion") Folks, if no objections materialize, into #for-next it goes.