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: <1193024720.3197.13.camel@raven.themaw.net> Date: Mon, 22 Oct 2007 11:45:19 +0800 From: Ian Kent <raven@...maw.net> To: Rik van Riel <riel@...hat.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org Subject: Re: 2.6.23-mm1 - autofs broken On Sat, 2007-10-20 at 01:13 -0400, Rik van Riel wrote: > On Thu, 11 Oct 2007 21:31:26 -0700 > Andrew Morton <akpm@...ux-foundation.org> wrote: > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23/2.6.23-mm1/ > > > > - I've been largely avoiding applying anything since rc8-mm2 in an > > attempt to stabilise things for the 2.6.23 merge. > > Between rc8-mm2 and 2.6.23-mm1, autofs stopped working in the > -mm kernel. > > Instead of mounting my home directory, I get these messages in > /var/log/messages: > > Oct 20 00:38:52 kenny automount[2293]: cache_readlock: mapent cache > rwlock lock failed This is quite strange, normally it should never fail and, in all the time version 5 has been available the maximum number of read locks has never been exceeded. Is there anything unusual going on like a server down causing autofs to issue a number of mounts that are all waiting to time out? > Oct 20 00:38:52 kenny automount[2293]: unexpected pthreads error: 11 at > 65 in cache.c Mmm .. if this is a genuine autofs issue maybe I need to handle EAGAIN returns but that would mean blocking which probably isn't good and I'd rather not if we can avoid it. > > I am not sure if this is due to autofs changes or changes in some other > code that was merged. If you can think of any suspicious change that > I should test, please let me know. > Is there anything in the log, an autofs4 kernel trace perhaps? Ian - 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