Re: PROBLEM: syzkaller found / reduced C repro for non-fatal unchecked MSR access error

‐‐‐ Original Message ‐‐‐ On Friday, January 11, 2019 8:59 AM, Peter Zijlstra wrote: > On Fri, Jan 11, 2019 at 01:37:50PM +, Esme wrote: > > > ‐‐‐ Original Message ‐‐‐ > > On Friday, January 11, 2019 5:02 AM, Peter Zijlstra pet...@infradead.org > > wrote: > > > > > On Thu,

Re: PROBLEM: syzkaller found / reduced C repro for non-fatal unchecked MSR access error

On Fri, Jan 11, 2019 at 01:37:50PM +, Esme wrote: > ‐‐‐ Original Message ‐‐‐ > On Friday, January 11, 2019 5:02 AM, Peter Zijlstra > wrote: > > > On Thu, Jan 10, 2019 at 11:21:16PM +, Esme wrote: > > > > > Attached is a fairly small C repro I did not see any references to > > >

Re: PROBLEM: syzkaller found / reduced C repro for non-fatal unchecked MSR access error

‐‐‐ Original Message ‐‐‐ On Friday, January 11, 2019 5:02 AM, Peter Zijlstra wrote: > On Thu, Jan 10, 2019 at 11:21:16PM +, Esme wrote: > > > Attached is a fairly small C repro I did not see any references to > > this possible flaw (unchecked MSR access) in relation to > >

Re: PROBLEM: syzkaller found / reduced C repro for non-fatal unchecked MSR access error

On Thu, Jan 10, 2019 at 11:21:16PM +, Esme wrote: > Attached is a fairly small C repro I did not see any references to > this possible flaw (unchecked MSR access) in relation to > __NR_perf_event_open > > Attached is the config directly extracted from proc. This is the call > stack in