[next-lockdown,0/1] debugfs EPERM fix for 'Kernel lockdown for secure boot' patch series

Message ID	cover.thread-bfac1b.your-ad-here.call-01542799656-ext-6093@work.hours (mailing list archive)
Headers	show Return-Path: <linux-security-module-owner@kernel.org> Gateway: Authorized Use Only! Violators will be prosecuted for <linux-security-module@vger.kernel.org> from <gor@linux.ibm.com>; Wed, 21 Nov 2018 12:05:14 -0000 Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 21 Nov 2018 12:05:11 -0000 Date: Wed, 21 Nov 2018 13:05:09 +0100 From: Vasily Gorbik <gor@linux.ibm.com> To: David Howells <dhowells@redhat.com>, James Morris <jmorris@namei.org> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org Subject: [PATCH next-lockdown 0/1] debugfs EPERM fix for 'Kernel lockdown for secure boot' patch series References: <4136.1522452584@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4136.1522452584@warthog.procyon.org.uk> Message-Id: <cover.thread-bfac1b.your-ad-here.call-01542799656-ext-6093@work.hours> Sender: owner-linux-security-module@vger.kernel.org Precedence: bulk
Series	debugfs EPERM fix for 'Kernel lockdown for secure boot' patch series \| expand [next-lockdown,0/1] debugfs EPERM fix for 'Kernel lockdown for secure boot' patch series [next-lockdown,1/1] debugfs: avoid EPERM when no open file operation defined

Message ID

cover.thread-bfac1b.your-ad-here.call-01542799656-ext-6093@work.hours (mailing list archive)

Headers

Date: Wed, 21 Nov 2018 13:05:09 +0100
From: Vasily Gorbik <gor@linux.ibm.com>
To: David Howells <dhowells@redhat.com>,
        James Morris <jmorris@namei.org>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [PATCH next-lockdown 0/1] debugfs EPERM fix for 'Kernel lockdown for
 secure boot' patch series
References: <4136.1522452584@warthog.procyon.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <4136.1522452584@warthog.procyon.org.uk>
Message-Id: 
 <cover.thread-bfac1b.your-ad-here.call-01542799656-ext-6093@work.hours>
Sender: owner-linux-security-module@vger.kernel.org
Precedence: bulk

Series

debugfs EPERM fix for 'Kernel lockdown for secure boot' patch series | expand

Message

Vasily Gorbik Nov. 21, 2018, 12:05 p.m. UTC

Not sure whom to offer the fix, since 'Kernel lockdown for secure boot'
in not upstream, but it has been picked by fedora and ubuntu. And I see
it in next-lockdown branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git

So, in addition to (prior to) opening bug reports to distributions I'm
sending this patch hoping to reach its origin from where distributions
had picked it.

Vasily Gorbik (1):
  debugfs: avoid EPERM when no open file operation defined

 fs/debugfs/file.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)