Message-Id: <200302172244.h1HMi3n03557@mail.osdl.org>
To: Andrew Morton <akpm@digeo.com>
cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, cliffw@osdl.org
Subject: Re: 2.5.61-mm1 
In-Reply-To: Message from Andrew Morton <akpm@digeo.com> 
   of "Fri, 14 Feb 2003 23:13:56 PST." <20030214231356.59e2ef51.akpm@digeo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 17 Feb 2003 14:44:03 -0800
From: Cliff White <cliffw@osdl.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1509
Lines: 33

> 
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.61/2.5.61-mm1/
> 
> . Jens has fixed the request queue aliasing problem and we are no longer
>   able to break the IO scheduler.  This was preventing the OSDL team from
>   running dbt2 against recent kernels, so hopefully that is all fixed up now.
> 
Thanks again for doing all this, really appreciate it.
Well, we're closer....
The showstopper for us is still the flock() issue. We have Mathew Wilcox's patch from
2.5.52, which we have been applying to all recent kernels. The patch is in PLM as patch id
# 1061. The issue is in BugMe as bug #94 . 
Without proper flock() we cannot stop and restart the database, which means we can't run the test. 
We've tried applying Wilcox's flock patch to -mm1, but it's doesn't go clean, and frankly we're not smart enough
to do the merge by hand -  lock code scares us. 

We just tested 2.5.61 vanilla, and 2.5.61-mm1. 

The patch applies cleanly to stock 2.5.61, and we can cycle the database.
We can't run dbt2 on stock 2.5.61, because of the scheduler bug. 
We believe the scheduler fix in -mm1 will be the ticket, but we can't try
it because of the flock() issue. So we're wedged. 
Can someone smarter than us maybe do a merge? 

thanks,
cliffw


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/