From: Gabriel Krisman Bertazi <gabriel@krisman.be>
To: Karan Sanghavi <karansanghvi98@gmail.com>
Cc: "Hugh Dickins" <hughd@google.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"André Almeida" <andrealmeid@igalia.com>,
"Christian Brauner" <brauner@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH] mm: shmem: Fix variable type to int to evaluate negative conditions
Date: Mon, 11 Nov 2024 13:37:43 -0500 [thread overview]
Message-ID: <87ttcdwr9k.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <20241111-unsignedcompare1601569-v1-1-c4a9c3c75a52@gmail.com> (Karan Sanghavi's message of "Mon, 11 Nov 2024 17:10:14 +0000")
Karan Sanghavi <karansanghvi98@gmail.com> writes:
> version variable captures return value from utf8_parse_version
> function which can be negative, but unsigned won't
> let it capture, thus missing the further checks on negative values.
>
> Fixes: 58e55efd6c72 ("tmpfs: Add casefold lookup support")
> Signed-off-by: Karan Sanghavi <karansanghvi98@gmail.com>
> ---
> Coverity Message:
> CID 1601569: (#1 of 1): Unsigned compared against 0 (NO_EFFECT)
> unsigned_compare: This less-than-zero comparison of an unsigned
> value is never true. version < 0U
Reviewed-by: Gabriel Krisman Bertazi <gabriel@krisman.be>
>
> Coverity Link:
> https://scan7.scan.coverity.com/#/project-view/10043/11354?selectedIssue=1601569
> ---
> mm/shmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/shmem.c b/mm/shmem.c
> index 7987deb2be9b..17a1d4fa8870 100644
> --- a/mm/shmem.c
> +++ b/mm/shmem.c
> @@ -4367,7 +4367,7 @@ static int shmem_parse_opt_casefold(struct fs_context *fc, struct fs_parameter *
> bool latest_version)
> {
> struct shmem_options *ctx = fc->fs_private;
> - unsigned int version = UTF8_LATEST;
> + int version = UTF8_LATEST;
> struct unicode_map *encoding;
> char *version_str = param->string + 5;
>
>
> ---
> base-commit: 6d59cab07b8d74d0f0422b750038123334f6ecc2
> change-id: 20241111-unsignedcompare1601569-05b5932145ef
>
> Best regards,
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2024-11-11 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 17:10 Karan Sanghavi
2024-11-11 17:19 ` André Almeida
2024-11-11 18:37 ` Gabriel Krisman Bertazi [this message]
2024-11-24 8:02 ` Karan Sanghavi
2024-11-24 11:33 ` Markus Elfring
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=87ttcdwr9k.fsf@mailhost.krisman.be \
--to=gabriel@krisman.be \
--cc=akpm@linux-foundation.org \
--cc=andrealmeid@igalia.com \
--cc=brauner@kernel.org \
--cc=hughd@google.com \
--cc=karansanghvi98@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=skhan@linuxfoundation.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