All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] cve: Fix kernel symbol finding for meltdown case
Date: Wed, 21 Aug 2019 12:01:33 -0400 (EDT)	[thread overview]
Message-ID: <145293056.7577705.1566403293117.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1566376044-175216-1-git-send-email-zhe.he@windriver.com>



----- Original Message -----
> From: He Zhe <zhe.he@windriver.com>
> 
> meltdown case fails as below.
> safe_file_ops.c:219: BROK: Expected 3 conversions got 2 at meltdown.c:272
> 
> find_kernel_symbol is defined to try twice with each of /proc/kallsyms and
> /boot/System.map-%s. Currently if the symbol is not found in /proc/kallsyms,
> when kernel option CONFIG_KALLSYMS_ALL is disabled, it would stop the case
> immediately due to SAFE_FILE_LINES_SCANF.
> 
> This patch turns to use FILE_LINES_SCANF to give find_kernel_symbol second
> chance.

That explains it, thanks for the patch.

We should also tweak TCONF condition in find_kernel_symbol - no need
to re-post for that, I can add that.

> 
> Signed-off-by: He Zhe <zhe.he@windriver.com>
> ---
>  testcases/cve/meltdown.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/testcases/cve/meltdown.c b/testcases/cve/meltdown.c
> index f78c38b..2d66c1e 100644
> --- a/testcases/cve/meltdown.c
> +++ b/testcases/cve/meltdown.c
> @@ -255,7 +255,7 @@ find_symbol_in_file(const char *filename, const char
> *symname)
>  
>  	sprintf(fmt, "%%lx %%c %s%%c", symname);
>  
> -	ret = SAFE_FILE_LINES_SCANF(filename, fmt, &addr, &type, &read);
> +	ret = FILE_LINES_SCANF(filename, fmt, &addr, &type, &read);
>  	if (ret)
>  		return 0;
>  
> --
> 2.7.4
> 
> 

  reply	other threads:[~2019-08-21 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21  8:27 [LTP] [PATCH v2] cve: Fix kernel symbol finding for meltdown case zhe.he
2019-08-21 16:01 ` Jan Stancek [this message]
2019-08-22 12:37   ` Jan Stancek

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=145293056.7577705.1566403293117.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ltp@lists.linux.it \
    /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.