The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Bruno Meneguele <bmeneg@redhat.com>
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ima: silence measurement list hexdump during kexec
Date: Wed, 22 Dec 2021 17:13:56 -0500	[thread overview]
Message-ID: <31d71e1957e84d2440f41d43d2570b112e91a27b.camel@linux.ibm.com> (raw)
In-Reply-To: <20211222191623.376174-1-bmeneg@redhat.com>

Hi Bruno,

On Wed, 2021-12-22 at 16:16 -0300, Bruno Meneguele wrote:
> The measurement list is dumped during a soft reset (kexec) through the call
> to "print_hex_dump(KERN_DEBUG, ...)", which ignores the DEBUG build flag.
> Instead, use "print_hex_dump_debug(...)", honoring the build flag.
> 
> Signed-off-by: Bruno Meneguele <bmeneg@redhat.com>

The patch description needs to at least explain why using
print_hex_dump() isn't sufficent.   Look at how print_hex_dump() is
defined.  Based on whether CONFIG_DYNAMIC_DEBUG is enabled, different
functions are used.

Mimi

> ---
>  security/integrity/ima/ima_kexec.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/security/integrity/ima/ima_kexec.c b/security/integrity/ima/ima_kexec.c
> index f799cc278a9a..13753136f03f 100644
> --- a/security/integrity/ima/ima_kexec.c
> +++ b/security/integrity/ima/ima_kexec.c
> @@ -61,9 +61,9 @@ static int ima_dump_measurement_list(unsigned long *buffer_size, void **buffer,
>  	}
>  	memcpy(file.buf, &khdr, sizeof(khdr));
>  
> -	print_hex_dump(KERN_DEBUG, "ima dump: ", DUMP_PREFIX_NONE,
> -			16, 1, file.buf,
> -			file.count < 100 ? file.count : 100, true);
> +	print_hex_dump_debug("ima dump: ", DUMP_PREFIX_NONE, 16, 1,
> +			     file.buf, file.count < 100 ? file.count : 100,
> +			     true);
>  
>  	*buffer_size = file.count;
>  	*buffer = file.buf;



  reply	other threads:[~2021-12-22 22:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 19:16 [PATCH] ima: silence measurement list hexdump during kexec Bruno Meneguele
2021-12-22 22:13 ` Mimi Zohar [this message]
2021-12-24 13:14   ` Bruno Meneguele

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=31d71e1957e84d2440f41d43d2570b112e91a27b.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=bmeneg@redhat.com \
    --cc=linux-integrity@vger.kernel.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