From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sedat Dilek Subject: Re: linux-next: Tree for January 15 (Call Trace in fs/dcache.c + autofs4) Date: Sat, 15 Jan 2011 12:44:19 +0100 Message-ID: References: <20110115075723.GJ19804@ZenIV.linux.org.uk> <20110115090702.GK19804@ZenIV.linux.org.uk> <20110115110848.GL19804@ZenIV.linux.org.uk> <20110115113445.GM19804@ZenIV.linux.org.uk> Reply-To: sedat.dilek@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Stephen Rothwell , linux-next@vger.kernel.org, LKML , linux-fsdevel To: Al Viro Return-path: In-Reply-To: <20110115113445.GM19804@ZenIV.linux.org.uk> Sender: linux-next-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Jan 15, 2011 at 12:34 PM, Al Viro wro= te: > On Sat, Jan 15, 2011 at 12:16:29PM +0100, Sedat Dilek wrote: > >> Which version do you mean by "mainline"? 2.6.37-git12? >> And with "[mismerge][foldme] breakage in __do_follow_link()" patch [= 1]? >> I have to look by pulling-in(to) Linus-tree (linux-next) which patch= es >> are not merged already. > > -git12 would do. =C2=A0Without any extra patches. =C2=A0Can you repro= duce the > ext3 oops on that alone? > Just a short answer (on the go... weekend shopping)... Currently, I am on a lame IBM T40p (Pentium-M) and doing a "full" build= =2E Unfortunately, I started a next linux-next build with the two patches from vfs-2.6#for-next. When I return I will try this kernel. If things aren't OK, I do a mainline build afterwards (w/o any patches)= =2E - Sedat -