From: Mimi Zohar <zohar@linux.ibm.com>
To: Joe Perches <joe@perches.com>,
Shuah Khan <skhan@linuxfoundation.org>,
jmorris@namei.org, serge@hallyn.com, mpe@ellerman.id.au,
erichte@linux.ibm.com, nayna@linux.ibm.com,
yuehaibing@huawei.com
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] security/integrity: Include __func__ in messages for easier debug
Date: Mon, 03 Feb 2020 08:21:17 -0500 [thread overview]
Message-ID: <1580736077.5585.4.camel@linux.ibm.com> (raw)
In-Reply-To: <ab2e19123cc15e3f8039b0d36e6ebae385db700e.camel@perches.com>
On Wed, 2020-01-29 at 19:08 -0800, Joe Perches wrote:
> On Wed, 2020-01-29 at 19:01 -0700, Shuah Khan wrote:
> > Change messages to messages to make it easier to debug. The following
> > error message isn't informative enough to figure out what failed.
> > Change messages to include function information.
> >
> > Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
> > ---
> > .../integrity/platform_certs/load_powerpc.c | 14 ++++++++------
> > security/integrity/platform_certs/load_uefi.c | 17 ++++++++++-------
> > 2 files changed, 18 insertions(+), 13 deletions(-)
> >
> > diff --git a/security/integrity/platform_certs/load_powerpc.c b/security/integrity/platform_certs/load_powerpc.c
>
> perhaps instead add #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
> so all the pr_<level> logging is more specific.
>
> This would prefix all pr_<level> output with "integrity: "
Agreed. Joe, could you post a patch with a proper patch description
for this?
thanks,
Mimi
next prev parent reply other threads:[~2020-02-03 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 2:01 [PATCH] security/integrity: Include __func__ in messages for easier debug Shuah Khan
2020-01-30 3:08 ` Joe Perches
2020-02-03 13:21 ` Mimi Zohar [this message]
2020-02-03 18:55 ` Shuah Khan
2020-02-03 19:02 ` Joe Perches
2020-02-03 19:20 ` Shuah Khan
2020-02-03 19:23 ` Casey Schaufler
2020-02-03 19:29 ` Joe Perches
2020-02-03 15:15 ` Nayna
2020-02-03 19:18 ` Joe Perches
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=1580736077.5585.4.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=erichte@linux.ibm.com \
--cc=jmorris@namei.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=nayna@linux.ibm.com \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.org \
--cc=yuehaibing@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.