Re: [PATCH 26/27] debugfs: Restrict debugfs when the kernel is locked down

2019-04-25 Thread Matthew Garrett
On Thu, Apr 25, 2019 at 3:49 AM Vasily Gorbik wrote: > I would appreciate if you consider that change, possibly just > squashing into yours. Thanks, I've squashed that in.

Re: [PATCH 26/27] debugfs: Restrict debugfs when the kernel is locked down

2019-04-25 Thread Vasily Gorbik
On Wed, Mar 06, 2019 at 03:59:12PM -0800, Matthew Garrett wrote: > From: David Howells > > static int open_proxy_open(struct inode *inode, struct file *filp) > { > struct dentry *dentry = F_DENTRY(filp); > @@ -147,6 +166,11 @@ static int open_proxy_open(struct inode *inode, struct >

[PATCH 26/27] debugfs: Restrict debugfs when the kernel is locked down

2019-03-06 Thread Matthew Garrett
From: David Howells Disallow opening of debugfs files that might be used to muck around when the kernel is locked down as various drivers give raw access to hardware through debugfs. Given the effort of auditing all 2000 or so files and manually fixing each one as necessary, I've chosen to

[PATCH 26/27] debugfs: Restrict debugfs when the kernel is locked down

2019-02-28 Thread Matthew Garrett
From: David Howells Disallow opening of debugfs files that might be used to muck around when the kernel is locked down as various drivers give raw access to hardware through debugfs. Given the effort of auditing all 2000 or so files and manually fixing each one as necessary, I've chosen to