linux-kernel - Re: [PATCH]: Fix Ultrastor asm snippet

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: <20110520142459.4c37d3e0@lxorguk.ukuu.org.uk>
Date:	Fri, 20 May 2011 14:24:59 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Samuel Thibault <samuel.thibault@...-lyon.org>,
	James.Bottomley@...e.de, linux-kernel@...r.kernel.org,
	linux-scsi@...r.kernel.org, akpm@...ux-foundation.org
Subject: Re: [PATCH]: Fix Ultrastor asm snippet

On Fri, 20 May 2011 09:02:15 -0400
Christoph Hellwig <hch@...radead.org> wrote:

> On Wed, May 18, 2011 at 05:06:05PM +0200, Samuel Thibault wrote:
> > Commit 1292500b replaced
> > 
> > "=m" (*field) : "1" (*field)
> > 
> > with
> > 
> > "=m" (*field) :
> > 
> > with comment "The following patch fixes it by using the '+' operator on
> > the (*field) operand, marking it as read-write to gcc."
> > '+' was actually forgotten.  This really puts it.
> 
> Do you actually have the hardware or was this just a code audit?
> 
> I have the strong suspicion that this driver is pretty much dead and
> bitrotting.

There are a pile of scsi drivers like the Ultrastor that probably want
retiring via staging.

I can believe an AHA152x or two lurk around, and the odd NCR53c80 and
clones because they were so voluminous but the rest I doubt somewhat.
--
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/