From: Luis Henriques <luis@igalia.com>
To: Jan Kara <jack@suse.cz>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Bernd Schubert <bschubert@ddn.com>,
Dave Chinner <david@fromorbit.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Matt Harvey <mharvey@jumptrading.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] vfs: export invalidate_inodes()
Date: Tue, 18 Feb 2025 13:35:26 +0000 [thread overview]
Message-ID: <8734gb8jfl.fsf@igalia.com> (raw)
In-Reply-To: <ze23goaoxiryaczmik3y66p23c35tf3ipfw27prlozrqciqlap@6lmpmsx7xsy3> (Jan Kara's message of "Tue, 18 Feb 2025 12:59:37 +0100")
On Tue, Feb 18 2025, Jan Kara wrote:
> On Sun 16-02-25 16:50:07, Luis Henriques wrote:
>> Signed-off-by: Luis Henriques <luis@igalia.com>
>
> Please use evict_inodes(). It is already exported and does exactly the same
> these days. We should really merge the patch deleting invalidate_inodes()
> :)
Thank you for the suggestion, Jan. Yeah that makes sense, of course.
However, since it's still not clear what's the future of this patchset
will be, I'll hold on re-sending it for now, but I'll definitely replace
invalidate_inodes() in a future revision.
Cheers,
--
Luís
>
> Honza
>
>> ---
>> 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);
>>
>> /*
>> * Isolate the inode from the LRU in preparation for freeing it.
>> diff --git a/fs/internal.h b/fs/internal.h
>> index e7f02ae1e098..7cb515cede3f 100644
>> --- a/fs/internal.h
>> +++ b/fs/internal.h
>> @@ -207,7 +207,6 @@ bool in_group_or_capable(struct mnt_idmap *idmap,
>> * fs-writeback.c
>> */
>> extern long get_nr_dirty_inodes(void);
>> -void invalidate_inodes(struct super_block *sb);
>>
>> /*
>> * dcache.c
>> diff --git a/include/linux/fs.h b/include/linux/fs.h
>> index 2c3b2f8a621f..ff016885646e 100644
>> --- a/include/linux/fs.h
>> +++ b/include/linux/fs.h
>> @@ -3270,6 +3270,7 @@ extern void discard_new_inode(struct inode *);
>> extern unsigned int get_next_ino(void);
>> extern void evict_inodes(struct super_block *sb);
>> void dump_mapping(const struct address_space *);
>> +extern void invalidate_inodes(struct super_block *sb);
>>
>> /*
>> * Userspace may rely on the inode number being non-zero. For example, glibc
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
next prev parent reply other threads:[~2025-02-18 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-16 16:50 [PATCH v5 0/2] fuse: allow notify_inval for all inodes Luis Henriques
2025-02-16 16:50 ` [PATCH v5 1/2] vfs: export invalidate_inodes() Luis Henriques
2025-02-18 11:59 ` Jan Kara
2025-02-18 13:35 ` Luis Henriques [this message]
2025-02-16 16:50 ` [PATCH v5 2/2] fuse: add new function to invalidate cache for all inodes Luis Henriques
2025-02-17 0:40 ` Bernd Schubert
2025-02-17 10:07 ` Luis Henriques
2025-02-17 10:29 ` Bernd Schubert
2025-02-17 11:47 ` Luis Henriques
2025-02-18 11:57 ` Jan Kara
2025-02-18 13:28 ` Luis Henriques
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=8734gb8jfl.fsf@igalia.com \
--to=luis@igalia.com \
--cc=brauner@kernel.org \
--cc=bschubert@ddn.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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