linux-kernel - Re: [PATCH] sparse: use identifiers to define address spaces

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wi=y6XoZKjxoGf9h4Zj3SPZnA+g5ZjsZ2hKT-AZW7H0ag@mail.gmail.com>
Date:   Thu, 18 Jun 2020 09:59:05 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     kernel test robot <lkp@...el.com>
Cc:     Luc Van Oostenryck <luc.vanoostenryck@...il.com>,
        kbuild-all@...ts.01.org, LKML <linux-kernel@...r.kernel.org>,
        Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Subject: Re: [PATCH] sparse: use identifiers to define address spaces

On Thu, Jun 18, 2020 at 3:06 AM kernel test robot <lkp@...el.com> wrote:
>
> I love your patch! Perhaps something to improve:

The new warnings don't seem to be due to the kernel test robot having
an old version of sparse, but just because the error strings changed,
and presumably the kernel test robot has some "ignore old sparse
warnings" logic.

So the warnings all look new, even if they aren't.

I'm planning on applying that patch soon, so this is just a heads-up
that that will (again) cause the big number of warning string changes,
but hopefully that will be a one-time event and the test robot will
learn.

             Linus