Re: [PATCH] um: Fix kcov crash before kernel is started.

2017-10-14 Thread Richard Weinberger
Am Samstag, 14. Oktober 2017, 00:00:25 CEST schrieb Thomas Meyer: > UMLs current_thread_info() unconditionally assumes that the top of the stack > contains the thread_info structure. > Prevent kcov from using invalid curent_thread_info() data by disable > instrumentation of early startup code. >

Re: [PATCH] um: Fix kcov crash before kernel is started.

2017-10-14 Thread Richard Weinberger
Am Samstag, 14. Oktober 2017, 00:00:25 CEST schrieb Thomas Meyer: > UMLs current_thread_info() unconditionally assumes that the top of the stack > contains the thread_info structure. > Prevent kcov from using invalid curent_thread_info() data by disable > instrumentation of early startup code. >

[PATCH] um: Fix kcov crash before kernel is started.

2017-10-13 Thread Thomas Meyer
UMLs current_thread_info() unconditionally assumes that the top of the stack contains the thread_info structure. Prevent kcov from using invalid curent_thread_info() data by disable instrumentation of early startup code. Signed-off-by: Thomas Meyer ---

[PATCH] um: Fix kcov crash before kernel is started.

2017-10-13 Thread Thomas Meyer
UMLs current_thread_info() unconditionally assumes that the top of the stack contains the thread_info structure. Prevent kcov from using invalid curent_thread_info() data by disable instrumentation of early startup code. Signed-off-by: Thomas Meyer --- arch/um/kernel/skas/Makefile | 2 ++

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-10 Thread Mark Rutland
gt;> > To: Richard Weinberger <rich...@nod.at> > >> > Cc: user-mode-linux-de...@lists.sourceforge.net, > >> > linux-kernel@vger.kernel.org > >> > Subject: Re: [PATCH] um: Fix kcov crash before kernel is started. > >> > User-Agent: NeoMutt/2017

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-10 Thread Mark Rutland
gt; Cc: user-mode-linux-de...@lists.sourceforge.net, > >> > linux-kernel@vger.kernel.org > >> > Subject: Re: [PATCH] um: Fix kcov crash before kernel is started. > >> > User-Agent: NeoMutt/20170113 (1.7.2) > >> > > >> > On Sun, Oct 08, 2017 a

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-10 Thread Dmitry Vyukov
> > Date: Sun, 8 Oct 2017 13:18:24 +0200 >> > From: Thomas Meyer <tho...@m3y3r.de> >> > To: Richard Weinberger <rich...@nod.at> >> > Cc: user-mode-linux-de...@lists.sourceforge.net, >> > linux-kernel@vger.kernel.org >> > Subject: Re: [

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-10 Thread Dmitry Vyukov
n, 8 Oct 2017 13:18:24 +0200 >> > From: Thomas Meyer >> > To: Richard Weinberger >> > Cc: user-mode-linux-de...@lists.sourceforge.net, >> > linux-kernel@vger.kernel.org >> > Subject: Re: [PATCH] um: Fix kcov crash before kernel is started. >> >

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-09 Thread Thomas Meyer
light on this topic? > > Any help is greatly appreciated! > > > > With kind regards > > thomas > > > > Date: Sun, 8 Oct 2017 13:18:24 +0200 > > From: Thomas Meyer <tho...@m3y3r.de> > > To: Richard Weinberger <rich...@nod.at> > > Cc: user-

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-09 Thread Thomas Meyer
appreciated! > > > > With kind regards > > thomas > > > > Date: Sun, 8 Oct 2017 13:18:24 +0200 > > From: Thomas Meyer > > To: Richard Weinberger > > Cc: user-mode-linux-de...@lists.sourceforge.net, > > linux-kernel@vger.kernel.org > >

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-09 Thread Dmitry Vyukov
gt; > Date: Sun, 8 Oct 2017 13:18:24 +0200 > From: Thomas Meyer <tho...@m3y3r.de> > To: Richard Weinberger <rich...@nod.at> > Cc: user-mode-linux-de...@lists.sourceforge.net, linux-kernel@vger.kernel.org > Subject: Re: [PATCH] um: Fix kcov crash before kernel is started.

Re: [tho...@m3y3r.de: Re: [PATCH] um: Fix kcov crash before kernel is started.]

2017-10-09 Thread Dmitry Vyukov
:18:24 +0200 > From: Thomas Meyer > To: Richard Weinberger > Cc: user-mode-linux-de...@lists.sourceforge.net, linux-kernel@vger.kernel.org > Subject: Re: [PATCH] um: Fix kcov crash before kernel is started. > User-Agent: NeoMutt/20170113 (1.7.2) > > On Sun, Oct 08, 2017 at 12:44:12PM +020

Re: [PATCH] um: Fix kcov crash before kernel is started.

2017-10-08 Thread Thomas Meyer
On Sun, Oct 08, 2017 at 12:44:12PM +0200, Richard Weinberger wrote: > 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 >

Re: [PATCH] um: Fix kcov crash before kernel is started.

2017-10-08 Thread Thomas Meyer
On Sun, Oct 08, 2017 at 12:44:12PM +0200, Richard Weinberger wrote: > 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 >

Re: [PATCH] um: Fix kcov crash before kernel is started.

2017-10-08 Thread Richard Weinberger
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: >

Re: [PATCH] um: Fix kcov crash before kernel is started.

2017-10-08 Thread Richard Weinberger
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: >

[PATCH] um: Fix kcov crash before kernel is started.

2017-10-08 Thread 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

[PATCH] um: Fix kcov crash before kernel is started.

2017-10-08 Thread 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