lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c249c855-aae6-4020-9ace-3b9528fd8422@web.de>
Date: Sun, 24 Nov 2024 12:33:27 +0100
From: Markus Elfring <Markus.Elfring@....de>
To: Karan Sanghavi <karansanghvi98@...il.com>, linux-mm@...ck.org,
 André Almeida <andrealmeid@...lia.com>,
 Andrew Morton <akpm@...ux-foundation.org>,
 Christian Brauner <brauner@...nel.org>,
 Gabriel Krisman Bertazi <gabriel@...sman.be>, Hugh Dickins <hughd@...gle.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
 Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH] mm: shmem: Fix variable type to int to evaluate negative
 conditions

…
> ---
> Coverity Message:
> CID 1601569: (#1 of 1): Unsigned compared against 0 (NO_EFFECT)
…

Can such information become a part of the change description?


Would a summary phrase like “Use signed data type for version handling
in shmem_parse_opt_casefold()” be more appropriate?

Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ