linux-kernel - Re: [PATCH] sparse: use static inline for __chk_{user,io}

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: <CANiq72njPaiPgTKWhZ696Nr+jDiTN1Vqu0ML8DdK==sjSnS1aw@mail.gmail.com>
Date:   Sat, 29 Aug 2020 09:33:31 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Cc:     linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sparse: use static inline for __chk_{user,io}_ptr()

Hi Luc,

On Fri, Aug 28, 2020 at 10:15 PM Luc Van Oostenryck
<luc.vanoostenryck@...il.com> wrote:
>
> But to the bot, any change to the content of the warning itself
> or its associated info is presented as a new warning.
> I've talked to the bot's guys about this problem and they've
> replied that they're seriously considering to change this behaviour.

I see! Well, I guess having a "false positive" is OK in that case. It
makes us look twice.

Thanks, queued!

Cheers,
Miguel