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

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: <cover.thread-bfac1b.your-ad-here.call-01542799656-ext-6093@work.hours>
Date:   Wed, 21 Nov 2018 13:05:09 +0100
From:   Vasily Gorbik <gor@...ux.ibm.com>
To:     David Howells <dhowells@...hat.com>,
        James Morris <jmorris@...ei.org>
Cc:     Martin Schwidefsky <schwidefsky@...ibm.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: [PATCH next-lockdown 0/1] debugfs EPERM fix for 'Kernel lockdown for
 secure boot' patch series

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