public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Luis Henriques <luis@igalia.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	Bernd Schubert <bschubert@ddn.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	Matt Harvey <mharvey@jumptrading.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] vfs: export invalidate_inodes()
Date: Tue, 18 Feb 2025 11:39:23 +1100	[thread overview]
Message-ID: <Z7PWuwQApEWI8b06@dread.disaster.area> (raw)
In-Reply-To: <20250217133228.24405-2-luis@igalia.com>

On Mon, Feb 17, 2025 at 01:32:27PM +0000, Luis Henriques wrote:
> Signed-off-by: Luis Henriques <luis@igalia.com>
> ---
>  fs/inode.c         | 1 +
>  fs/internal.h      | 1 -
>  include/linux/fs.h | 1 +
>  3 files changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/inode.c b/fs/inode.c
> index 5587aabdaa5e..88387ecb2c34 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -939,6 +939,7 @@ void invalidate_inodes(struct super_block *sb)
>  
>  	dispose_list(&dispose);
>  }
> +EXPORT_SYMBOL(invalidate_inodes);

Oh, I didn't realise the FUSE core wasn't built in. That makes me
even less enthusiastic about this....

Ok, if this is going to happen, you need to pull in the change I
made to get rid of invalidate_inodes() because it is now a duplicate of
evict_inodes(). evict_inodes() is already EXPORT_SYMBOL_GPL(), so
then this patch goes away.

-Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2025-02-18  0:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 13:32 [PATCH v6 0/2] fuse: allow notify_inval for all inodes Luis Henriques
2025-02-17 13:32 ` [PATCH v6 1/2] vfs: export invalidate_inodes() Luis Henriques
2025-02-18  0:39   ` Dave Chinner [this message]
2025-02-17 13:32 ` [PATCH v6 2/2] fuse: add new function to invalidate cache for all inodes Luis Henriques
2025-02-18  0:55   ` Dave Chinner
2025-02-18  9:15     ` Miklos Szeredi
2025-02-18 10:04       ` Luis Henriques
2025-02-18 10:34         ` Miklos Szeredi
2025-02-18 11:51           ` Luis Henriques
2025-02-18 14:26             ` Miklos Szeredi
2025-02-18 18:11               ` Luis Henriques
2025-02-18 22:05                 ` Dave Chinner
2025-02-19 11:23                   ` Luis Henriques
2025-02-19 15:39                     ` Miklos Szeredi
2025-02-19 16:31                       ` Luis Henriques
2025-02-18 21:29               ` Dave Chinner
2025-02-18 21:44       ` Dave Chinner
2025-02-18  9:07   ` Miklos Szeredi

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=Z7PWuwQApEWI8b06@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=brauner@kernel.org \
    --cc=bschubert@ddn.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis@igalia.com \
    --cc=mharvey@jumptrading.com \
    --cc=miklos@szeredi.hu \
    --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