Re: [PATCH V37 19/29] Lock down module params that specify hardware parameters (eg. ioport)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH V37 19/29] Lock down module params that specify hardware parameters (eg. ioport)
From: Matthew Garrett <mjg59@xxxxxxxxxx>
Date: Thu, 1 Aug 2019 13:44:10 -0700
Cc: James Morris <jmorris@xxxxxxxxx>, LSM List <linux-security-module@xxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Linux API <linux-api@xxxxxxxxxxxxxxx>, David Howells <dhowells@xxxxxxxxxx>, Alan Cox <gnomes@xxxxxxxxxxxxxxxxxxx>, Kees Cook <keescook@xxxxxxxxxxxx>
In-reply-to: <20190801161933.GB5834@linux-8ccs>
References: <20190731221617.234725-1-matthewgarrett@google.com> <20190731221617.234725-20-matthewgarrett@google.com> <20190801161933.GB5834@linux-8ccs>

On Thu, Aug 1, 2019 at 9:19 AM Jessica Yu <jeyu@xxxxxxxxxx> wrote:

> Hm, I don't think the doing parameter ended up being used in this function?

Thanks for catching that, I'll fix.

References:
- [PATCH V37 00/29] security: Add support for locking down the kernel
  - From: Matthew Garrett
- [PATCH V37 19/29] Lock down module params that specify hardware parameters (eg. ioport)
  - From: Matthew Garrett
- Re: [PATCH V37 19/29] Lock down module params that specify hardware parameters (eg. ioport)
  - From: Jessica Yu

Prev by Date: Re: [PATCH V37 04/29] Enforce module signatures if the kernel is locked down
Next by Date: Re: [PATCHv5 25/37] x86/vdso: Switch image on setns()/clone()
Previous by thread: Re: [PATCH V37 19/29] Lock down module params that specify hardware parameters (eg. ioport)
Next by thread: [PATCH V37 18/29] Lock down TIOCSSERIAL
Index(es):
- Date
- Thread

[Index of Archives] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux