linux-kernel - Re: [OOPS] 2.6.21-rc6-git5 in cfq_dispatch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070425101857.GR9715@kernel.dk>
Date:	Wed, 25 Apr 2007 12:18:57 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Brad Campbell <brad@...p.net.au>
Cc:	Neil Brown <neilb@...e.de>, Chuck Ebbert <cebbert@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [OOPS] 2.6.21-rc6-git5 in cfq_dispatch_insert

On Wed, Apr 25 2007, Brad Campbell wrote:
> Jens Axboe wrote:
> 
> >It looks to be extremely rare. Aliases are extremely rare, front merges
> >are rare. And you need both to happen with the details you outlined. But
> >it's a large user base, and we've had 3-4 reports on this in the past
> >months. So it obviously does happen. I could not make it trigger without
> >doctoring the unplug code when I used aio.
> 
> Well, not that rare on this particular machine (I had a case where I could 
> reproduce it in less than an hour of normal use previously on this box), 
> and I've had it occur a number of times on my servers, I just never 
> reported it before as I never took the time to set up a serial console and 
> capture the oops.

Extremely rare in the sense that it takes md and some certain conditions
to happen for it to trigger. So for most people it'll be extremely rare,
and for others (such as yourself) that hit it, it wont be so rare :-)

> >Here's a fix for it, confirmed.
> 
> Shall I leave the other debugging in, apply this and run it for a few hard 
> days?

Yes, that would be perfect!

-- 
Jens Axboe

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