Date: Mon, 25 Oct 2004 12:05:24 +0200
From: Jens Axboe <axboe@suse.de>
To: Lorenzo Allegrucci <l_allegrucci@yahoo.it>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-mm1 oops
Message-ID: <20041025100524.GE8306@suse.de>
References: <200410231731.21778.l_allegrucci@yahoo.it> <200410241620.50438.l_allegrucci@yahoo.it> <200410242202.17981.l_allegrucci@yahoo.it> <200410251045.09370.l_allegrucci@yahoo.it> <20041025085542.GD8306@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20041025085542.GD8306@suse.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1169
Lines: 31

On Mon, Oct 25 2004, Jens Axboe wrote:
> On Mon, Oct 25 2004, Lorenzo Allegrucci wrote:
> > On Sunday 24 October 2004 22:02, Lorenzo Allegrucci wrote:
> > > On Sunday 24 October 2004 16:20, Lorenzo Allegrucci wrote:
> > > > On Sunday 24 October 2004 14:30, Jens Axboe wrote:
> > > > > On Sat, Oct 23 2004, Lorenzo Allegrucci wrote:
> > > > > > 
> > > > > > 100% reproducible with elevator=cfq
> > > > > 
> > > > > but not with the other io schedulers?
> > > > 
> > > > No, now I can reproduce it with the anticipatory scheduler too.
> > > 
> > > I've just got the same oops using XFS instead of ext3.
> > 
> > And disabling CONFIG_PREEMPT_BKL doesn't help.
> 
> I'll try to reproduce it here now.

Something fishy is going on here - it seems to happen in the if (ret)
cleanup in direct_io_worker(), last error was -EFAULT for this case. And
reverting the dio eof patch 'fixes' the bug, I don't know why yet.

-- 
Jens Axboe

-
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/