On Fri, Dec 22 2006, Vasily Tarasov wrote: > Unfortunately this fix exists already in 2.6.19... So it is, hmmm. I don't have time to look into this right now (I'll be gone between tonight and new years), but with a bit of git skills, you should be able to narrow it down. -- Jens Axboe