From: Julian Sun <sunjunchao2870@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
brauner@kernel.org
Subject: Re: [PATCH] vfs: return -EOVERFLOW in generic_remap_checks() when overflow check fails
Date: Fri, 06 Sep 2024 19:12:08 +0800 [thread overview]
Message-ID: <d6ddc03e3aa86af60b13e9ebb81548b18fe6d74c.camel@gmail.com> (raw)
In-Reply-To: <20240906102942.egowavntfx6t3z6t@quack3>
On Fri, 2024-09-06 at 12:29 +0200, Jan Kara wrote:
Sure, I will include this patch in the patch set for the next version.
But I think it maybe deserves a separate patch, rather than being
integrated into the original patch?
> On Fri 06-09-24 11:32:02, Julian Sun wrote:
> > Keep it consistent with the handling of the same check within
> > generic_copy_file_checks().
> > Also, returning -EOVERFLOW in this case is more appropriate.
> >
> > Signed-off-by: Julian Sun <sunjunchao2870@gmail.com>
>
> Well, you were already changing this condition here [1] so maybe just
> update the errno in that patch as well? No need to generate unnecessary
> patch conflicts...
>
> [1] https://lore.kernel.org/all/20240905121545.ma6zdnswn5s72byb@quack3
>
> Honza
>
> > ---
> > fs/remap_range.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/remap_range.c b/fs/remap_range.c
> > index 28246dfc8485..97171f2191aa 100644
> > --- a/fs/remap_range.c
> > +++ b/fs/remap_range.c
> > @@ -46,7 +46,7 @@ static int generic_remap_checks(struct file *file_in, loff_t pos_in,
> >
> > /* Ensure offsets don't wrap. */
> > if (pos_in + count < pos_in || pos_out + count < pos_out)
> > - return -EINVAL;
> > + return -EOVERFLOW;
> >
> > size_in = i_size_read(inode_in);
> > size_out = i_size_read(inode_out);
> > --
> > 2.39.2
> >
Thanks,
--
Julian Sun <sunjunchao2870@gmail.com>
next prev parent reply other threads:[~2024-09-06 11:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 3:32 [PATCH] vfs: return -EOVERFLOW in generic_remap_checks() when overflow check fails Julian Sun
2024-09-06 10:29 ` Jan Kara
2024-09-06 11:12 ` Julian Sun [this message]
2024-09-09 10:08 ` Jan Kara
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=d6ddc03e3aa86af60b13e9ebb81548b18fe6d74c.camel@gmail.com \
--to=sunjunchao2870@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).