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: Re: Switching to iterate_shared
Date: Thu, 18 Aug 2022 15:35:18 +0100 [thread overview]
Message-ID: <Yv5OJuwJq17bQDXo@casper.infradead.org> (raw)
In-Reply-To: <Yvvr447B+mqbZAoe@casper.infradead.org>
On Tue, Aug 16, 2022 at 08:11:31PM +0100, Matthew Wilcox wrote:
> 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?
I just checked ADFS. This isn't a f_ops ->iterate, this is a special
adfs_dir_ops. ADFS already uses f_ops->iterate_shared.
next prev parent reply other threads:[~2022-08-18 14:36 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 ` Switching to iterate_shared Matthew Wilcox
2022-08-16 20:14 ` 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 [this message]
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=Yv5OJuwJq17bQDXo@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).