From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Leesoo Ahn <lsahn@ooseel.net>
Cc: "Carlos Llamas" <cmllamas@google.com>,
"Leesoo Ahn" <lsahn@wewakecorp.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Todd Kjos" <tkjos@android.com>,
"Martijn Coenen" <maco@android.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Christian Brauner" <brauner@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] android: binder: print error message on failure of creating proc file
Date: Fri, 12 Jul 2024 09:19:02 +0200 [thread overview]
Message-ID: <2024071241-entail-icing-58cf@gregkh> (raw)
In-Reply-To: <CANTT7qi_qZfFH+T1z22GMQ-LmG1vHG1adzD=hxXiXyKT4kkhOQ@mail.gmail.com>
On Fri, Jul 12, 2024 at 03:52:32PM +0900, Leesoo Ahn wrote:
> 2024년 7월 12일 (금) 오후 1:01, Carlos Llamas <cmllamas@google.com>님이 작성:
> >
> > On Fri, Jul 12, 2024 at 12:21:40PM +0900, Leesoo Ahn wrote:
> > > It better prints out an error message to give more information if
> > > calling debugfs_create_file() is failure and the return value has an
> > > error code.
> > >
> > > Signed-off-by: Leesoo Ahn <lsahn@ooseel.net>
> > > ---
> >
> > What are you trying to fix? My understanding is that users of the
> > debugfs API can safely ignore any errors and move on. IMO it doesn't
> > make sense to add this without a real reason.
>
> What I was trying to say, users would predict that a file under
> debugfs will be created while they are opening a binder device. But if
> it failed for some reason without any debug message, they would get
> confused that the file doesn't exist and have no clue what happened
> without a message.
And that's fine, again, the kernel does not care if debugfs is working
or not. It's just a debugging help, it does not affect the normal
operation of a system at all, and as such, userspace can't rely on it
being present for any functionality other than debugging issues that
might happen at times.
thanks,
greg k-h
next prev parent reply other threads:[~2024-07-12 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 3:21 Leesoo Ahn
2024-07-12 4:01 ` Carlos Llamas
2024-07-12 5:39 ` Greg Kroah-Hartman
2024-07-12 6:52 ` Leesoo Ahn
2024-07-12 7:19 ` Greg Kroah-Hartman [this message]
2024-07-12 7:33 ` Leesoo Ahn
2024-07-12 5:40 ` Greg Kroah-Hartman
2024-07-12 5:54 ` Leesoo Ahn
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=2024071241-entail-icing-58cf@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=arve@android.com \
--cc=brauner@kernel.org \
--cc=cmllamas@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsahn@ooseel.net \
--cc=lsahn@wewakecorp.com \
--cc=maco@android.com \
--cc=surenb@google.com \
--cc=tkjos@android.com \
/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
all inboxes | Powered by JetHome®