lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 22 Jul 2019 22:57:04 -0400 From: Waiman Long <longman@...hat.com> To: Luis Henriques <lhenriques@...e.com> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Borislav Petkov <bp@...en8.de>, Will Deacon <will.deacon@....com>, huang ying <huang.ying.caritas@...il.com>, Peter Zijlstra <peterz@...radead.org>, Jeff Layton <jlayton@...nel.org>, the arch/x86 maintainers <x86@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, Tim Chen <tim.c.chen@...ux.intel.com>, Ingo Molnar <mingo@...hat.com>, Davidlohr Bueso <dave@...olabs.net>, Linux List Kernel Mailing <linux-kernel@...r.kernel.org>, "H. Peter Anvin" <hpa@...or.com> Subject: Re: [PATCH v8 13/19] locking/rwsem: Make rwsem->owner an atomic_long_t On 7/21/19 4:49 PM, Luis Henriques wrote: > Waiman Long <longman@...hat.com> writes: > >> On 7/20/19 4:41 AM, Luis Henriques wrote: >>> "Linus Torvalds" <torvalds@...ux-foundation.org> writes: >>> >>>> On Fri, Jul 19, 2019 at 12:32 PM Waiman Long <longman@...hat.com> wrote: >>>>> This patch shouldn't change the behavior of the rwsem code. The code >>>>> only access data within the rw_semaphore structures. I don't know why it >>>>> will cause a KASAN error. I will have to reproduce it and figure out >>>>> exactly which statement is doing the invalid access. >>>> The stack traces should show line numbers if you run them through >>>> scripts/decode_stacktrace.sh. >>>> >>>> You need to have debug info enabled for that, though. >>>> >>>> Luis? >>>> >>>> Linus >>> Yep, sure. And I should have done this in the initial report. It's a >>> different trace, I had to recompile the kernel. >>> >>> (I'm also adding Jeff to the CC list.) >>> >>> Cheers, >> Thanks for the information. I think I know where the problem is. Would >> you mind applying the attached patch to see if it can fix the KASAN error. > Yep, that seems to work -- I can't reproduce the error anymore (and > sorry for the delay). Thanks! And feel free to add my Tested-by. > > Cheers, Thanks for the testing. I will post the official patch tomorrow. Cheers, Longman
Powered by blists - more mailing lists