| 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: <48748340.1060603@msgid.tls.msk.ru> Date: Wed, 09 Jul 2008 13:22:08 +0400 From: Michael Tokarev <mjt@....msk.ru> To: Oliver Neukum <oliver@...kum.org> CC: Linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: 2.6.25: random stalls on certain hardware - regression? Oliver Neukum wrote: > Am Dienstag 08 Juli 2008 23:56:12 schrieb Michael Tokarev: > >> Any idea how to start welcome. Meanwhile I'll try current 2.6.26pre, >> in a hope it will not destroy all our data.. ;) > > Can you test whether select() triggers the lockup? Hmm. Sure I can, and it definitely uses select() here and there - samba & Oracle8 & cronyd & vtund & syslogd - that's services running on it all using select(2). Can you elaborate a bit more on this please? I mean, should it lock up on first select() (so that it's not what I see here) or on some random one (still may be the situation I see), or not so-random which is more-or-less possible to trigger? Thank you for the reply! /mjt -- 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