linux-kernel - Re: [PATCH] sparse doesn't support indirect

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <a9b65d60-a3c0-f46a-c10e-5d649e75d9ce@infradead.org>
Date:   Tue, 27 Feb 2018 14:30:03 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Matthew Wilcox <willy@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sparse doesn't support indirect_branch attribute

On 02/27/2018 02:12 PM, Linus Torvalds wrote:
> On Tue, Feb 27, 2018 at 12:18 PM, Randy Dunlap <rdunlap@...radead.org> wrote:
>>
>> I don't mind the patch, but I did send a patch for this attribute on Feb. 13, 2018,
>> to the sparse mailing list.
> 
> I think the sparse plan is to just stop warning about unknown
> attributes, because it doesn't really help users (at most it's a note
> to a sparse developer).

Yes, there are sparse discussions about that.

There is also a kernel kbuild patch from Luc that Masahiro has also merged that
does -Wno-unknown-attributes (or however that is spelled).

> But sparse doesn't have the same regular releases the kernel has. Oh well.

Right.


-- 
~Randy