linux-kernel - Re: [PATCH] ARM: mmp: replace NO

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]

Date:   Tue, 6 Sep 2016 13:03:42 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Russell King - ARM Linux <linux@...linux.org.uk>
Cc:     Arnd Bergmann <arnd@...db.de>, Eric Miao <eric.y.miao@...il.com>,
        Haojian Zhuang <haojian.zhuang@...il.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: mmp: replace NO_IRQ

On Tue, Sep 6, 2016 at 12:44 PM, Russell King - ARM Linux
<linux@...linux.org.uk> wrote:
>
> My point still stands though.  Merely hiding it doesn't make the problem
> go away - it's just the same problem but now it won't be as visible, and
> as such it'll probably never get resolved.

How much of a legacy thing is this?

The main reason I'd like to _really_ make NO_IRQ go away is that it
seems that some people copy it from existing drivers, or just think
it's the RightThing(tm) to do because it looks so plausible.

So in that sense I wouldn't actually mind "merely hiding it".

It may not *fix* that particular driver or subsystem, but if it's
sufficiently well hidden or specialized, at least it won't cause the
pattern to be copied in the future, I'd hope.

So hiding things inside a particular driver (or a particular
subsystem) may be hacky from the standpoint of that particular driver
or subsystem, but from a "big issue" standpoint I don't mind at all.

           Linus