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: Thu, 19 Nov 2015 13:46:29 +0100 From: Stefan Priebe - Profihost AG <s.priebe@...fihost.ag> To: Hannes Frederic Sowa <hannes@...essinduktion.org>, Florian Weimer <fweimer@...hat.com> Cc: Thomas Gleixner <tglx@...utronix.de>, netdev@...r.kernel.org, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: Asterisk deadlocks since Kernel 4.1 Am 19.11.2015 um 13:41 schrieb Hannes Frederic Sowa: > On Thu, Nov 19, 2015, at 12:43, Stefan Priebe - Profihost AG wrote: >> >> Am 19.11.2015 um 12:41 schrieb Hannes Frederic Sowa: >>> On Thu, Nov 19, 2015, at 10:56, Stefan Priebe - Profihost AG wrote: >>>> OK it had a livelock again. It just took more time. >>>> >>>> So here is the data: >>> >>> Thanks, I couldn't reproduce it so far with simple threaded resolver >>> loop on your kernel. :/ >>> >>> Your data is useless if you don't also provide the file descriptor which >>> you are blocking on right now. ;) >>> >>> Thanks, >>> Hannes >> >> ah sorry. So we need the gdb backtrace with the rcvmsg and then the fd >> list + netlink list? > > Yes, albeit the probability we find something new is minimal. We already > know it blocks deep down in netlink code. I tried to reproduce it in > multithreaded environment with no results so far. Can you even try a > newer kernel? I can try Kernel 4.4-rc1 next week. Or something else? Stefan > > Bye, > Hannes > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists