linux-kernel - Re: [PATCH 01/39] Annotate module params that specify hardware parameters (eg. ioport)

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: <20161206105008.GA9900@kroah.com>
Date:   Tue, 6 Dec 2016 11:50:08 +0100
From:   Greg KH <gregkh@...uxfoundation.org>
To:     David Howells <dhowells@...hat.com>
Cc:     One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>,
        linux-kernel@...r.kernel.org,
        linux-security-module@...r.kernel.org, keyrings@...r.kernel.org,
        minyard@....org
Subject: Re: [PATCH 01/39] Annotate module params that specify hardware
 parameters (eg. ioport)

On Tue, Dec 06, 2016 at 10:42:47AM +0000, David Howells wrote:
> Greg KH <gregkh@...uxfoundation.org> wrote:
> 
> > What about all of the ways you can change ioports dynamically from
> > ioctls?  Or can't python write ioctls to device nodes?  :)
> 
> Do you mean change the ioport a driver uses by ioctl or actually read/write an
> ioport directly?

change the ioport a driver uses.  The tty layer can do this for UARTs
through an ioctl (can't remember which one off the top of my head,
sorry, it gets reported as a bug by the syscall fuzzers every other year
or so when they crash the kernel randomly...)

> Do the following patches that I've already posted address your issues:
> 
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/commit/?h=efi-lock-down&id=c67c338dd82d28c67d38eb3147368eb36dbf1c16
> 
> http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/commit/?h=efi-lock-down&id=10bd7277eef5194ba038fc2d907bac9e6aeab12b
> 
> They're going to be in a patchset that I am/was intending to sit atop the
> module parameter-lockdown patchset.

Ah, I hadn't seen those, that's a good start, and does close some other
places.

thanks,

greg k-h