From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Michal Suchánek" <msuchanek@suse.de>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
Matthew Garrett <matthewgarrett@google.com>,
James Morris <jmorris@namei.org>,
David Howells <dhowells@redhat.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] debugfs: lockdown: Allow reading debugfs files that are not world readable
Date: Thu, 6 Jan 2022 15:48:30 +0100 [thread overview]
Message-ID: <YdcBPmzaoibUEg4K@kroah.com> (raw)
In-Reply-To: <20220105131222.GG117207@kunlun.suse.cz>
On Wed, Jan 05, 2022 at 02:12:22PM +0100, Michal Suchánek wrote:
> Hello,
>
> On Wed, Jan 05, 2022 at 12:51:31PM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Jan 04, 2022 at 06:05:05PM +0100, Michal Suchanek wrote:
> > >
> > > When the kernel is locked down the kernel allows reading only debugfs
> > > files with mode 444. Mode 400 is also valid but is not allowed.
> > >
> > > Make the 444 into a mask.
> > >
> > > Fixes: 5496197f9b08 ("debugfs: Restrict debugfs when the kernel is locked down")
> > > Signed-off-by: Michal Suchanek <msuchanek@suse.de>
> > > ---
> > > fs/debugfs/file.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Why has it taken so long for anyone to notice this (2 years!)?
> >
> > Is that because no one uses the lockdown mode and tries to read debugfs
> > files?
>
> It's because people use those LTSS kernels that don't have this change.
>
> > >
> > > diff --git a/fs/debugfs/file.c b/fs/debugfs/file.c
> > > index 7d162b0efbf0..950c63fa4d0b 100644
> > > --- a/fs/debugfs/file.c
> > > +++ b/fs/debugfs/file.c
> > > @@ -147,7 +147,7 @@ static int debugfs_locked_down(struct inode *inode,
> > > struct file *filp,
> > > const struct file_operations *real_fops)
> > > {
> > > - if ((inode->i_mode & 07777) == 0444 &&
> > > + if ((inode->i_mode & 07777 & ~0444) == 0 &&
> >
> > You are now allowing more than just 0400, is that intentional?
>
> The intent is to allow files that have permissions that are subset of
> 0444. The only one that makes sense and people complain about is 0400
> but if you had 0440 or 0004 it would be permitted as well.
>
> > I never understood why files that were 0666 were not able to be read
> > here as well, why not allow that as well? What was magic about 0444
> > files?
>
> I don't understand that either but I am not really trying to challenge
> that part.
Fair enough. I don't care about the locked-down mode stuff, so I'll go
queue this up now, thanks!
greg k-h
prev parent reply other threads:[~2022-01-06 14:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 17:05 [PATCH] debugfs: lockdown: Allow reading debugfs files that are not world readable Michal Suchanek
2022-01-05 11:51 ` Greg Kroah-Hartman
2022-01-05 13:12 ` Michal Suchánek
2022-01-06 14:48 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YdcBPmzaoibUEg4K@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=andy.shevchenko@gmail.com \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthewgarrett@google.com \
--cc=msuchanek@suse.de \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox