linux-kernel - Re: [GIT PULL] SPI updates for v6.8

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]

Date: Mon, 22 Jan 2024 19:57:01 +0100
From: Klaus Kudielka <klaus.kudielka@...il.com>
To: Mark Brown <broonie@...nel.org>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] SPI updates for v6.8

On Mon, 2024-01-22 at 18:38 +0000, Mark Brown wrote:
> On Mon, Jan 22, 2024 at 07:30:09PM +0100, Klaus Kudielka wrote:
> > On Sun, 2024-01-07 at 22:38 +0000, Mark Brown wrote:
> 
> > I just booted 6.8.0-rc1 on Turris Omnia (CONFIG_SPI_ORION=y,
> > device tree: arch/arm/boot/dts/marvell/armada-385-turris-omnia.dts)
> 
> > and got the following error:
> > 
> > [    0.090231] spi_master spi0: No. of CS is more than max. no. of supported CS
> > [    0.097358] spi_master spi0: Failed to create SPI device for /soc/spi@...00/flash@0
> > 
> > End result: the three MTD partitions I used to have on the SPI-NOR are gone.
> 
> Actualy looking at the DT it's not immediately obvious why this is
> triggering - there's only one chip select in use, numbered 0 AFAICT.
> Anyway, if you could test the patch I linked hopefully it does fix the
> issue.

I wouldn't have an explanation either. But said patch, applied on top of 6.8.0-rc1,
seems to be a possible cure. Everything nominal again, AFAICT.

[    0.191427] 3 fixed-partitions partitions found on MTD device spi0.0
[    0.191440] Creating 3 MTD partitions on "spi0.0":
[    0.191446] 0x000000000000-0x0000000f0000 : "U-Boot"
[    0.191656] 0x000000100000-0x000000800000 : "Rescue system"
[    0.191796] 0x0000000f0000-0x000000100000 : "u-boot-env"

Thanks, Klaus