From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lkdtm: no need to check return value of debugfs_create functions
Date: Tue, 11 Jun 2019 20:56:56 +0200 [thread overview]
Message-ID: <20190611185656.GB4659@kroah.com> (raw)
In-Reply-To: <201906111144.3E05EAA80@keescook>
On Tue, Jun 11, 2019 at 11:44:53AM -0700, Kees Cook wrote:
> On Tue, Jun 11, 2019 at 08:32:13PM +0200, Greg Kroah-Hartman wrote:
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do something different based on this.
>
> What is the user-visible feedback when, say, debugfs_create_file()
> fails?
All of the memory in your system is now gone and it would have long
locked up a while before this call ever happened :)
And no user functionality should ever change if a debugfs call fails, or
succeeds, this is debugging only.
> And what happens when debugfs_create_file() passes in a NULL root?
The file ends up in the root of debugfs. But as this can only happen if
the system is dead, I wouldn't worry about it.
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-11 18:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 18:32 [PATCH] lkdtm: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-06-11 18:44 ` Kees Cook
2019-06-11 18:56 ` Greg Kroah-Hartman [this message]
2019-06-11 20:43 ` Kees Cook
2019-06-12 11:36 ` Greg Kroah-Hartman
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=20190611185656.GB4659@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
/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