From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Kent Subject: Re: Linux 2.6.26-rc4 Date: Fri, 06 Jun 2008 10:39:12 +0800 Message-ID: <1212719953.3035.3.camel@raven.themaw.net> References: <47107.195.41.66.226.1212486572.squirrel@mail.jabbernet.dk> <20080603095713.GR28946@ZenIV.linux.org.uk> <5440.195.41.66.226.1212487482.squirrel@mail.jabbernet.dk> <20080603104035.GT28946@ZenIV.linux.org.uk> <20080603105258.GV28946@ZenIV.linux.org.uk> <1212499623.3025.46.camel@raven.themaw.net> <1212651099.3047.44.camel@raven.themaw.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Al Viro , Miklos Szeredi , jesper@krogh.cc, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Jeff Moyer , Andrew Morton To: Linus Torvalds Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2008-06-05 at 14:29 -0700, Linus Torvalds wrote: > > On Thu, 5 Jun 2008, Ian Kent wrote: > > > > Keep in mind this doesn't address any other autofs4 issues but I it > > should allow us to identify if this was in fact the root cause of the > > problem Jesper reported. > > Jesper, can you test this? I think you said you could trigger this in ~24 > hours or so? I'd love to have some testing of some heavy autofs user. Even > if it's not a guarantee of a fix (due to reproducing the bug not being > entirely trivial), at least I'd like to know that it doesn't introduce any > obvious new problems either.. I'm continuing to test this also. My initial testing was fine but late last night, with some of my other patches applied as well, I started seeing some strange problems. Ian