linux-kernel - Re: [PATCH 00/16] selftest/mm: Remove warnings found by adding compiler flags

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: <20250115213235.713d0c5af3269c318740b66f@linux-foundation.org>
Date: Wed, 15 Jan 2025 21:32:35 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Muhammad Usama Anjum <usama.anjum@...labora.com>
Cc: Kees Cook <kees@...nel.org>, Andy Lutomirski <luto@...capital.net>, Will
 Drewry <wad@...omium.org>, Shuah Khan <shuah@...nel.org>,
 Jérôme Glisse <jglisse@...hat.com>,
 linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-mm@...ck.org, kernel@...labora.com
Subject: Re: [PATCH 00/16] selftest/mm: Remove warnings found by adding
 compiler flags

On Thu,  9 Jan 2025 22:38:26 +0500 Muhammad Usama Anjum <usama.anjum@...labora.com> wrote:

> Recently, I reviewed a patch on the mm/kselftest mailing list about a
> test which had obvious type mismatch fix in it. It was strange why that
> wasn't caught during development and when patch was accepted. This led
> me to discover that those extra compiler options to catch these warnings
> aren't being used. When I added them, I found tens of warnings in just
> mm suite.
> 
> In this series, I'm fixing those warnings. The last check adds the
> compiler flags with which the warnings have been caught.

I'm seeing a couple of unresolved issues against this series so I'll drop
v1.  Please let's revisit after -rc1.

https://lkml.kernel.org/r/20250110190057.2294fd5a@pumpkin
https://lkml.kernel.org/r/d9c290e2-f22d-41be-aa68-2aebd3eb1a67@sirena.org.uk