From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, ceph-devel@vger.kernel.org,
coda@cs.cmu.edu, codalist@coda.cs.cmu.edu,
Namjae Jeon <linkinjeon@kernel.org>,
Sungjong Seo <sj1557.seo@samsung.com>,
jfs-discussion@lists.sourceforge.net, ocfs2-devel@oss.oracle.com,
devel@lists.orangefs.org, linux-unionfs@vger.kernel.org,
linux-security-module@vger.kernel.org, apparmor@lists.ubuntu.com,
Hans de Goede <hdegoede@redhat.com>
Subject: Switching to iterate_shared
Date: Tue, 16 Aug 2022 20:11:31 +0100 [thread overview]
Message-ID: <Yvvr447B+mqbZAoe@casper.infradead.org> (raw)
In-Reply-To: <CAHk-=wgkNwDikLfEkqLxCWR=pLi1rbPZ5eyE8FbfmXP2=r3qcw@mail.gmail.com>
On Tue, Aug 16, 2022 at 11:58:36AM -0700, Linus Torvalds wrote:
> That said, our filldir code is still confusing as hell. And I would
> really like to see that "shared vs non-shared" iterator thing go away,
> with everybody using the shared one - and filesystems that can't deal
> with it using their own lock.
>
> But that's a completely independent wart in our complicated filldir saga.
>
> But if somebody were to look at that iterate-vs-iterate_shared, that
> would be lovely. A quick grep shows that we don't have *that* many of
> the non-shared cases left:
>
> git grep '\.iterate\>.*='
>
> seems to imply that converting them to a "use my own load" wouldn't be
> _too_ bad.
>
> And some of them might actually be perfectly ok with the shared
> semantics (ie inode->i_rwsem held just for reading) and they just were
> never converted originally.
What's depressing is that some of these are newly added. It'd be
great if we could attach something _like_ __deprecated to things
that checkpatch could pick up on.
fs/adfs/dir_f.c: .iterate = adfs_f_iterate,
fs/adfs/dir_fplus.c: .iterate = adfs_fplus_iterate,
ADFS is read-only, so must be safe?
fs/ceph/dir.c: .iterate = ceph_readdir,
fs/ceph/dir.c: .iterate = ceph_readdir,
At least CEPH has active maintainers, cc'd
fs/coda/dir.c: .iterate = coda_readdir,
Would anyone notice if we broke CODA? Maintainers cc'd anyway.
fs/exfat/dir.c: .iterate = exfat_iterate,
Exfat is a new addition, but has active maintainers.
fs/jfs/namei.c: .iterate = jfs_readdir,
Maintainer cc'd
fs/ntfs/dir.c: .iterate = ntfs_readdir, /* Read directory contents. */
Maybe we can get rid of ntfs soon.
fs/ocfs2/file.c: .iterate = ocfs2_readdir,
fs/ocfs2/file.c: .iterate = ocfs2_readdir,
maintainers cc'd
fs/orangefs/dir.c: .iterate = orangefs_dir_iterate,
New; maintainer cc'd
fs/overlayfs/readdir.c: .iterate = ovl_iterate,
Active maintainer, cc'd
fs/proc/base.c: .iterate = proc_##LSM##_attr_dir_iterate, \
Hmm. We need both SMACK and Apparmor to agree to this ... cc's added.
fs/vboxsf/dir.c: .iterate = vboxsf_dir_iterate,
Also newly added. Maintainer cc'd.
next prev parent reply other threads:[~2022-08-16 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 16:11 [RFC][PATCH] Change calling conventions for filldir_t Al Viro
2022-08-16 16:24 ` Matthew Wilcox
2022-08-16 16:32 ` Al Viro
2022-08-16 16:57 ` Christian Brauner
2022-08-16 18:58 ` Linus Torvalds
2022-08-16 19:11 ` Matthew Wilcox [this message]
2022-08-16 20:14 ` Switching to iterate_shared Jan Harkes
2022-08-16 21:20 ` Matthew Wilcox
2022-08-16 22:58 ` Linus Torvalds
2022-08-17 7:25 ` Amir Goldstein
2022-08-17 17:05 ` Linus Torvalds
2022-08-17 20:13 ` Amir Goldstein
2022-08-16 22:30 ` Casey Schaufler
2022-08-16 23:09 ` Linus Torvalds
2022-08-18 14:35 ` Matthew Wilcox
2022-08-18 16:14 ` [apparmor] " John Johansen
2022-09-21 19:25 ` Mike Marshall
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=Yvvr447B+mqbZAoe@casper.infradead.org \
--to=willy@infradead.org \
--cc=apparmor@lists.ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=devel@lists.orangefs.org \
--cc=hdegoede@redhat.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=sj1557.seo@samsung.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).