linux-kernel - Re: [PATCH v2] spi: spi-imx: fix off-by-one in mx51 CPU mode burst length

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: <20240318172415.1588-1-adam@jessamine.co.uk>
Date: Mon, 18 Mar 2024 17:21:48 +0000
From: Adam Butcher <adam@...samine.co.uk>
To: broonie@...nel.org
Cc: adam@...samine.co.uk,
	benjamin@...ler.one,
	carlos.song@....com,
	kernel@...gutronix.de,
	linux-imx@....com,
	linux-kernel@...r.kernel.org,
	linux-spi@...r.kernel.org,
	s.hauer@...gutronix.de,
	shawnguo@...nel.org,
	stefanmoring@...il.com
Subject: Re: [PATCH v2] spi: spi-imx: fix off-by-one in mx51 CPU mode burst length

On Mon, March 18, 2024 3:55 pm, Mark Brown wrote:
> On Wed, Mar 13, 2024 at 08:58:19PM +0000, Adam Butcher wrote:
>> From: Adam Butcher <adam@...samine.co.uk>
>>
>> 992e1211dc91 ("spi: imx: fix the burst length at DMA mode and CPU
>> mode") corrects three cases of setting the ECSPI burst length but
>> erroneously leaves the in-range CPU case one bit to big (in that
>> field a value of 0 means 1 bit).  The effect was that transmissions
>> that should have been 8-bit bytes appeared as 9-bit causing failed
>> communication with SPI devices.
>
> This doesn't apply against current code, please check and resend.
>

That refers to the commit my patch fixes.  On looking it up I found it
was no longer reachable
(https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git/commit/?id=992e1211dc91).
The corresponding upstream commit that is reachable from both
torvalds/linux.git/master and broonie/spi.git/spi-next is c712c05e46c8.

Though it was made against 6.8.y, I was able to apply my patch with
git-am to both the latest broonie/spi.git/for-next (593c0afc18d) and
torvalds/linux.git/master (0a7b0acecea2) without conflicts.

Shall I send a v3 correcting the hash mentioned in the commit message?