From: Jeff Layton <jlayton@redhat.com>
To: Jeffle Xu <jefflexu@linux.alibaba.com>, dhowells@redhat.com
Cc: linux-fsdevel@vger.kernel.org, linux-cachefs@redhat.com
Subject: Re: [Linux-cachefs] [PATCH] netfs: fix parameter of cleanup()
Date: Tue, 07 Dec 2021 08:42:16 -0500 [thread overview]
Message-ID: <d621c5522bdee8113946e7d1e5e9822820e0ef5a.camel@redhat.com> (raw)
In-Reply-To: <20211207031449.100510-1-jefflexu@linux.alibaba.com>
On Tue, 2021-12-07 at 11:14 +0800, Jeffle Xu wrote:
> The order of these two parameters is just reversed. gcc didn't warn on
> that, probably because 'void *' can be converted from or to other
> pointer types without warning.
>
> Cc: stable@vger.kernel.org
> Fixes: 3d3c95046742 ("netfs: Provide readahead and readpage netfs helpers")
> Fixes: e1b1240c1ff5 ("netfs: Add write_begin helper")
> Signed-off-by: Jeffle Xu <jefflexu@linux.alibaba.com>
> ---
> fs/netfs/read_helper.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/netfs/read_helper.c b/fs/netfs/read_helper.c
> index 7046f9bdd8dc..4adcb0336ecf 100644
> --- a/fs/netfs/read_helper.c
> +++ b/fs/netfs/read_helper.c
> @@ -960,7 +960,7 @@ int netfs_readpage(struct file *file,
> rreq = netfs_alloc_read_request(ops, netfs_priv, file);
> if (!rreq) {
> if (netfs_priv)
> - ops->cleanup(netfs_priv, folio_file_mapping(folio));
> + ops->cleanup(folio_file_mapping(folio), netfs_priv);
> folio_unlock(folio);
> return -ENOMEM;
> }
> @@ -1191,7 +1191,7 @@ int netfs_write_begin(struct file *file, struct address_space *mapping,
> goto error;
> have_folio_no_wait:
> if (netfs_priv)
> - ops->cleanup(netfs_priv, mapping);
> + ops->cleanup(mapping, netfs_priv);
> *_folio = folio;
> _leave(" = 0");
> return 0;
> @@ -1202,7 +1202,7 @@ int netfs_write_begin(struct file *file, struct address_space *mapping,
> folio_unlock(folio);
> folio_put(folio);
> if (netfs_priv)
> - ops->cleanup(netfs_priv, mapping);
> + ops->cleanup(mapping, netfs_priv);
> _leave(" = %d", ret);
> return ret;
> }
Ouch, good catch.
Reviewed-by: Jeff Layton <jlayton@redhat.com>
prev parent reply other threads:[~2021-12-07 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 3:14 [PATCH] netfs: fix parameter of cleanup() Jeffle Xu
2021-12-07 13:42 ` Jeff Layton [this message]
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=d621c5522bdee8113946e7d1e5e9822820e0ef5a.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=dhowells@redhat.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).