Re: [PATCH v2] rbtree: fix the red root

2019-01-14 Thread Esme
Disabled kmemleak options. On mobile, pardon brevity. Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Monday, January 14, 2019 10:45 AM, Qian Cai wrote: > On 1/14/19 1:23 AM, Esme wrote: > > > I did not yet verify the previous branches but did tune

Re: [PATCH v2] rbtree: fix the red root

2019-01-13 Thread Esme
‐‐‐ Original Message ‐‐‐ On Sunday, January 13, 2019 11:52 PM, Douglas Gilbert wrote: > On 2019-01-13 10:59 p.m., Esme wrote: > > > ‐‐‐ Original Message ‐‐‐ > > On Sunday, January 13, 2019 10:52 PM, Douglas Gilbert dgilb...@interlog.com > > wrote: >

Re: [PATCH v2] rbtree: fix the red root

2019-01-13 Thread Esme
‐‐‐ Original Message ‐‐‐ On Sunday, January 13, 2019 10:52 PM, Douglas Gilbert wrote: > On 2019-01-13 10:07 p.m., Esme wrote: > > > ‐‐‐ Original Message ‐‐‐ > > On Sunday, January 13, 2019 9:33 PM, Qian Cai c...@lca.pw wrote: > > > > > On 1/1

Re: [PATCH v2] rbtree: fix the red root

2019-01-13 Thread Esme
; > > > above. > > > > > /* > > > > >    * If there is a black parent, we are done. > > > > >    * Otherwise, take some corrective action as, > > > > >    * per 4), we don't want a red root or two > > > > >    * consec

Re: [PATCH v2] rbtree: fix the red root

2019-01-11 Thread Esme
I've been out today but return home tomorrow and can test any suggested fixes, or with different kernel settings. Just let me know. Esme Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Friday, January 11, 2019 7:18 PM, Qian Cai wrote: > On 1/11/19 6:16 PM, Matt

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

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

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

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

Re: PROBLEM: syzkaller found / pool corruption-overwrite / page in user-area or NULL

2019-01-10 Thread Esme
‐‐‐ Original Message ‐‐‐ On Thursday, January 10, 2019 11:52 PM, Qian Cai wrote: > On 1/10/19 10:15 PM, Esme wrote: > > > > > [ 75.793150] RIP: 0010:rb_insert_color+0x189/0x1480 > > > > > > What's in that line? Try, > > > $ ./scripts/fa

Re: PROBLEM: syzkaller found / pool corruption-overwrite / page in user-area or NULL

2019-01-10 Thread Esme
> > [ 75.793150] RIP: 0010:rb_insert_color+0x189/0x1480 > > What's in that line? Try, > > $ ./scripts/faddr2line vmlinux rb_insert_color+0x189/0x1480 rb_insert_color+0x189/0x1480: __rb_insert at /home/files/git/linux/lib/rbtree.c:131 (inlined by) rb_insert_color at

Re: PROBLEM: syzkaller found / pool corruption-overwrite / page in user-area or NULL

2019-01-10 Thread Esme
The console debug/stacks/info from just now. The previous config, current kernel from github. -- Esme [ 75.783231] kasan: CONFIG_KASAN_INLINE enabled [ 75.785870] kasan: GPF could be caused by NULL-ptr deref or user memory access [ 75.787695] general protection fault: [#1] SMP KASAN

PROBLEM: syzkaller found / pool corruption-overwrite / page in user-area or NULL

2019-01-10 Thread Esme
this process moving forward as I'm still building out my test systems/debugging tools. Attached is the report and C repro that still triggers on a fresh git pull as of a few minutes ago, if you need anything else please let me know. Esme Linux syzkaller 5.0.0-rc1+ #5 SMP Tue Jan 8 20:39:33 EST 2019