From: Dan Carpenter <dan.carpenter@linaro.org>
To: Richard Lyu <richard.lyu@suse.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: staging: ipu3: img-mmu: fix sign-to-unsigned conversion
Date: Fri, 6 Mar 2026 16:02:48 +0300 [thread overview]
Message-ID: <aarQeHfQuq20gXH0@stanley.mountain> (raw)
In-Reply-To: <20260306104352.629177-1-richard.lyu@suse.com>
On Fri, Mar 06, 2026 at 06:43:59PM +0800, Richard Lyu wrote:
> imgu_mmu_unmap() returns size_t (unsigned), representing the number of
> bytes successfully unmapped. However, when the alignment check fails,
> it currently returns -EINVAL.
>
> On 64-bit systems, this negative error code is implicitly converted
> to a very large unsigned value (18446744073709551594),
That happens on a 32bit also, although of course, the number would be
smaller.
> incorrectly
> indicating that memory was unmapped and potentially breaking the
> caller's logic.
>
All the callers ignore the return value so it doesn't actually affect
anything. The commit message needs to say this.
> Return 0 when the alignment check fails to correctly indicate that
> no bytes were unmapped while resolving the following
> -Wsign-conversion warning:
>
> drivers/staging/media/ipu3/ipu3-mmu.c:393:24: warning: unsigned
> conversion from 'int' to 'size_t' {aka 'long unsigned int'} changes
> value from '-22' to '18446744073709551594' [-Wsign-conversion]
> 393 | return -EINVAL;
>
> Signed-off-by: Richard Lyu <richard.lyu@suse.com>
Please add a Fixes tag.
Otherwise, the fix looks okay to me.
regards,
dan carpenter
prev parent reply other threads:[~2026-03-06 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 10:43 [PATCH] media: staging: ipu3: img-mmu: fix sign-to-unsigned conversion Richard Lyu
2026-03-06 13:02 ` Dan Carpenter [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=aarQeHfQuq20gXH0@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=bingbu.cao@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=richard.lyu@suse.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@intel.com \
/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