Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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(-)

-- 
2.18.0.13.gd42ae10