[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.62.0804100822240.12367@office2.c1.internal>
Date: Thu, 10 Apr 2008 08:29:57 +0200 (CEST)
From: Allard Hoeve <allard@...e.nl>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Miklos Szeredi <miklos@...redi.hu>, jens.axboe@...cle.com,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Neil Brown <neilb@...e.de>,
Gertjan Oude Lohuis <gertjan@...e.nl>
Subject: Re: [patch] fix infinite loop in generic_file_splice_read()
Hallo Andrew, others,
> We found suspicious-looking code in generic_file_splice_read() back in
> February. See http://lkml.org/lkml/2008/2/29/443. I suspect that patch
> (if it works) will address the truncate lockup as well - it zaps the
> loop entirely.
>
> Unfortunately Allard never got back to us (probably because he's running
> 2.6.24 which has a quite different generic_file_splice_read()) and the
> patch didn't get anywhere.
Unfortunately, we cannot test the patch on the server that triggered the
bug in 2.6.24.2, because it's too critical for operation. On other similar
servers the bug hasn't been encountered and we were unable to reproduce
it, so it must be some combination of load and typical usage (NFS server).
We are now running 2.6.22.x, which does fine. I hope you understand our
hesitation of running patched, known-bugged kernels on our fileservers :)
Thanks for all the bughunting here. There is a maintenance window soon,
I'll try to put the original patch on the agenda.
Regards,
Allard Hoeve
--
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