All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] um: Fix kcov crash before kernel is started.
Date: Sun, 08 Oct 2017 12:44:12 +0200	[thread overview]
Message-ID: <2201510.o3ITaGZhUC@blindfold> (raw)
In-Reply-To: <20171008103158.14107-1-thomas@m3y3r.de>

Am Sonntag, 8. Oktober 2017, 12:31:58 CEST schrieb Thomas Meyer:
> UMLs current_thread_info() unconditionally assumes that the top of the stack
> contains the thread_info structure. But on UML the __sanitizer_cov_trace_pc
> function is called for *all* functions! This results in an early crash:
> 
> Prevent kcov from using invalid curent_thread_info() data by checking
> the system_state.
> 
> Signed-off-by: Thomas Meyer <thomas@m3y3r.de>
> ---
>  kernel/kcov.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/kernel/kcov.c b/kernel/kcov.c
> index 3f693a0f6f3e..d601c0e956f6 100644
> --- a/kernel/kcov.c
> +++ b/kernel/kcov.c
> @@ -56,6 +56,12 @@ void notrace __sanitizer_cov_trace_pc(void)
>  	struct task_struct *t;
>  	enum kcov_mode mode;
> 
> +#ifdef CONFIG_UML
> +	if(!(system_state == SYSTEM_SCHEDULING ||
> +	     system_state == SYSTEM_RUNNING))
> +		return;
> +#endif

Hmm, and why does it work on all other archs then?

Thanks,
//richard



  reply	other threads:[~2017-10-08 10:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 10:31 [PATCH] um: Fix kcov crash before kernel is started Thomas Meyer
2017-10-08 10:44 ` Richard Weinberger [this message]
2017-10-08 11:18   ` Thomas Meyer
  -- strict thread matches above, loose matches on Subject: below --
2017-10-10  8:59 [thomas@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.] Dmitry Vyukov
2017-10-13 22:00 ` [PATCH] um: Fix kcov crash before kernel is started Thomas Meyer
2017-10-14  8:05   ` Richard Weinberger

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=2201510.o3ITaGZhUC@blindfold \
    --to=richard@nod.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.de \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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.