| 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
| ||
|
Message-ID: <alpine.LFD.2.02.1203151503530.2466@ionos> Date: Thu, 15 Mar 2012 15:04:53 +0100 (CET) From: Thomas Gleixner <tglx@...utronix.de> To: Sasha Levin <levinsasha928@...il.com> cc: John Stultz <john.stultz@...aro.org>, Dave Jones <davej@...hat.com>, "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org> Subject: Re: ntp: BUG: spinlock lockup on CPU#1 On Thu, 15 Mar 2012, Sasha Levin wrote: > On Thu, Mar 15, 2012 at 3:23 PM, Sasha Levin <levinsasha928@...il.com> wrote: > > Hi all, > > > > I was doing some more fuzzing with trinity in a KVM tools guest, using > > today's linux-next, when I've experienced a complete system lockup > > (just in the guest ofcourse). After a bit I got the spew at the bottom > > of this mail. > > > > From what I can tell from the logs, there were several threads waiting > > on syscall results, and I suspect that the adjtimex() call on CPU3 is > > somehow responsible for this lockup. > > Oh, and I'm not sure if it's related or not, but I've started seeing > the following spew every time I start fuzzing: > > [ 47.105987] ------------[ cut here ]------------ > [ 47.106021] WARNING: at kernel/time/clockevents.c:209 It's unrelated, but I'm mighty curious how you manage that. Thanks, tglx -- 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