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.
>
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.
>
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
---
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 ++
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
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
> > 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: [
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.
>> >
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-
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
> >
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.
: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
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
>
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
>
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:
>
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:
>
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
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
18 matches
Mail list logo