From: Matthew Wilcox <willy@infradead.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: linux-cachefs@redhat.com, linux-fsdevel@vger.kernel.org,
linux-erofs@lists.ozlabs.org, David Howells <dhowells@redhat.com>,
Christian Brauner <christian@brauner.io>,
Jeff Layton <jlayton@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Chao Yu <chao@kernel.org>,
Yue Hu <huyue2@coolpad.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>
Subject: Re: [PATCH v2 3/4] erofs: Don't use certain internal folio_*() functions
Date: Mon, 15 Jan 2024 14:06:29 +0000 [thread overview]
Message-ID: <ZaU75cT0jx9Ya+6G@casper.infradead.org> (raw)
In-Reply-To: <20240115083337.1355191-1-hsiangkao@linux.alibaba.com>
On Mon, Jan 15, 2024 at 04:33:37PM +0800, Gao Xiang wrote:
> From: David Howells <dhowells@redhat.com>
>
> Filesystems should use folio->index and folio->mapping, instead of
> folio_index(folio), folio_mapping() and folio_file_mapping() since
> they know that it's in the pagecache.
>
> Change this automagically with:
>
> perl -p -i -e 's/folio_mapping[(]([^)]*)[)]/\1->mapping/g' fs/erofs/*.c
> perl -p -i -e 's/folio_file_mapping[(]([^)]*)[)]/\1->mapping/g' fs/erofs/*.c
> perl -p -i -e 's/folio_index[(]([^)]*)[)]/\1->index/g' fs/erofs/*.c
>
> Reported-by: Matthew Wilcox <willy@infradead.org>
> Signed-off-by: David Howells <dhowells@redhat.com>
> Reviewed-by: Jeff Layton <jlayton@kernel.org>
> Cc: Chao Yu <chao@kernel.org>
> Cc: Yue Hu <huyue2@coolpad.com>
> Cc: Jeffle Xu <jefflexu@linux.alibaba.com>
> Cc: linux-erofs@lists.ozlabs.org
> Cc: linux-fsdevel@vger.kernel.org
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> ---
> Hi folks,
>
> I tend to apply this patch upstream since compressed data fscache
> adaption touches this part too. If there is no objection, I'm
> going to take this patch separately for -next shortly..
Could you change the subject? It's not that the functions are
"internal", it's that filesystems don't need to use them because they're
guaranteed to not see swap pages. Maybe just s/internal/unnecessary/
> Thanks,
> Gao Xiang
>
> Change since v1:
> - a better commit message pointed out by Jeff Layton.
>
> fs/erofs/fscache.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/erofs/fscache.c b/fs/erofs/fscache.c
> index 87ff35bff8d5..bc12030393b2 100644
> --- a/fs/erofs/fscache.c
> +++ b/fs/erofs/fscache.c
> @@ -165,10 +165,10 @@ static int erofs_fscache_read_folios_async(struct fscache_cookie *cookie,
> static int erofs_fscache_meta_read_folio(struct file *data, struct folio *folio)
> {
> int ret;
> - struct erofs_fscache *ctx = folio_mapping(folio)->host->i_private;
> + struct erofs_fscache *ctx = folio->mapping->host->i_private;
> struct erofs_fscache_request *req;
>
> - req = erofs_fscache_req_alloc(folio_mapping(folio),
> + req = erofs_fscache_req_alloc(folio->mapping,
> folio_pos(folio), folio_size(folio));
> if (IS_ERR(req)) {
> folio_unlock(folio);
> @@ -276,7 +276,7 @@ static int erofs_fscache_read_folio(struct file *file, struct folio *folio)
> struct erofs_fscache_request *req;
> int ret;
>
> - req = erofs_fscache_req_alloc(folio_mapping(folio),
> + req = erofs_fscache_req_alloc(folio->mapping,
> folio_pos(folio), folio_size(folio));
> if (IS_ERR(req)) {
> folio_unlock(folio);
> --
> 2.39.3
>
next prev parent reply other threads:[~2024-01-15 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 8:33 Gao Xiang
2024-01-15 14:06 ` Matthew Wilcox [this message]
2024-01-15 14:39 ` Gao Xiang
2024-01-15 14:46 ` [PATCH v3 3/4] erofs: Don't use certain unnecessary " Gao Xiang
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 18:01 [PATCH 3/4] erofs: Don't use certain internal " David Howells
2024-01-15 8:34 ` [PATCH v2 " Gao Xiang
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=ZaU75cT0jx9Ya+6G@casper.infradead.org \
--to=willy@infradead.org \
--cc=chao@kernel.org \
--cc=christian@brauner.io \
--cc=dhowells@redhat.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=jlayton@kernel.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®