linux-kernel - Re: pata_cmd64x broken in 2.6.33-rc1 on sparc64

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20091220003701.7c5a0257@lxorguk.ukuu.org.uk>
Date:	Sun, 20 Dec 2009 00:37:01 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Meelis Roos <mroos@...ux.ee>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Linux IDE mailing list <linux-ide@...r.kernel.org>
Subject: Re: pata_cmd64x broken in 2.6.33-rc1 on sparc64

> > mice: PS/2 mouse device common for all mice
> > ------------[ cut here ]------------
> > WARNING: at drivers/ata/pata_cmd64x.c:268 cmd64x_bmdma_stop+0x3c/0x60()

Which version of the cmd64x patch got applied ?

> Does backing out the following commit fix things?
> 
> 	commit d43744390e460dce6626fb8de2c02a24ff650005
> 	Author: Alan Cox <alan@...ux.intel.com>
> 	Date:   Mon Nov 30 13:22:54 2009 +0000
> 
> 	    pata_cmd64x: implement serialization as per notes
> 
> Although quite unlikely, commit f0353813afe784330622596ff141e7525ccd99de 
> may also change things.  Try backing that out, if backing out the first 
> commit (d43744...) fails to improve behavior.

I'll take a look at this after new year but it looks like the old version
ended up in the libata tree without the additional fixes, if so its
pretty trivial to sort out (see Bartlomiej response to the original and
the follow up thread plus fixes)
--
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/