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: Tue, 13 Jan 2015 08:41:26 +0000 From: Thomas Graf <tgraf@...g.ch> To: Ying Xue <ying.xue@...driver.com> Cc: linux-kernel@...r.kernel.org, lkp@...org, Netdev <netdev@...r.kernel.org> Subject: Re: Fwd: [rhashtable] WARNING: CPU: 0 PID: 10 at kernel/locking/mutex.c:570 mutex_lock_nested() On 01/13/15 at 03:50pm, Ying Xue wrote: > On 01/12/2015 08:42 PM, Thomas Graf wrote: > > On 01/12/15 at 09:38am, Ying Xue wrote: > >> Hi Thomas, > >> > >> I am really unable to see where is wrong leading to below warning > >> complaints. Can you please help me check it? > > > > Not sure yet. It's not your patch that introduced the issue though. > > It merely exposed the affected code path. > > > > Just wondering, did you test with CONFIG_DEBUG_MUTEXES enabled? > > > > > > After I enable above option, I don't find similar complaints during my > testing. I can't reproduce it in my KVM box either so far. It looks like a mutex_lock() on an uninitialized mutex or use after free but I can't find such a code path so far. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists