linux-kernel - Re: [PATCH 27/39] Annotate hardware config module parameters in drivers/scsi/

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]

Date:   Wed, 05 Apr 2017 15:33:00 +0100
From:   David Howells <dhowells@...hat.com>
To:     Finn Thain <fthain@...egraphics.com.au>
Cc:     dhowells@...hat.com, linux-kernel@...r.kernel.org,
        Michael Schmitz <schmitzmic@...il.com>,
        Achim Leubner <achim_leubner@...ptec.com>,
        "James E.J. Bottomley" <jejb@...ux.vnet.ibm.com>,
        linux-scsi@...r.kernel.org,
        "Martin K. Petersen" <martin.petersen@...cle.com>,
        gnomes@...rguk.ukuu.org.uk, linux-security-module@...r.kernel.org,
        keyrings@...r.kernel.org, minyard@....org,
        "Juergen E. Fischer" <fischer@...bit.de>,
        Dario Ballabio <ballabio_dario@....com>
Subject: Re: [PATCH 27/39] Annotate hardware config module parameters in drivers/scsi/

Finn Thain <fthain@...egraphics.com.au> wrote:

> I can see how base addresses and IO ports are relevant, but the irq 
> parameter changes below don't protect the kernel image AFAICT. What's the 
> rationale for those changes? I think it should be stated here.

Easier grepping for one.  But I'm also currently preventing the changing of
any hardware parameters.  If a driver refuses to share an irq, you could use
it to deprive another driver of the ability to get an irq at all.

David