linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Harkes <jaharkes@cs.cmu.edu>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org
Subject: Re: Switching to iterate_shared
Date: Tue, 16 Aug 2022 16:14:38 -0400	[thread overview]
Message-ID: <20220816201438.66v4ilot5gvnhdwj@cs.cmu.edu> (raw)
In-Reply-To: <Yvvr447B+mqbZAoe@casper.infradead.org>

On Tue, Aug 16, 2022 at 03:35:46PM -0400, Matthew Wilcox wrote:
> fs/coda/dir.c:  .iterate        = coda_readdir,
> 
> Would anyone notice if we broke CODA?  Maintainers cc'd anyway.

Ha, yes I think I would notice, but probably not until after the changes
got released and trickled down to the distributions ;)

So good to know in advance a change like this is coming. I'll have to
educate myself on this shared vs non-shared filldir.

Jan


  reply	other threads:[~2022-08-16 20:14 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 [this message]
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=20220816201438.66v4ilot5gvnhdwj@cs.cmu.edu \
    --to=jaharkes@cs.cmu.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).