linux-kernel - Re: [PATCH next] spi: spi-qpic-snand: validate user/chip specific ECC properties

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] [day] [month] [year] [list]

Message-Id: <174729453999.272648.10698524382095396308.b4-ty@kernel.org>
Date: Thu, 15 May 2025 09:35:39 +0200
From: Mark Brown <broonie@...nel.org>
To: Varadarajan Narayanan <quic_varada@...cinc.com>, 
 Md Sadre Alam <quic_mdalam@...cinc.com>, 
 Sricharan Ramabadhran <quic_srichara@...cinc.com>, 
 Gabor Juhos <j4g8y7@...il.com>
Cc: linux-spi@...r.kernel.org, linux-mtd@...ts.infradead.org, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH next] spi: spi-qpic-snand: validate user/chip specific
 ECC properties

On Thu, 01 May 2025 18:19:16 +0200, Gabor Juhos wrote:
> The driver only supports 512 bytes ECC step size and 4 bit ECC strength
> at the moment, however it does not reject unsupported step/strength
> configurations. Due to this, whenever the driver is used with a flash
> chip which needs stronger ECC protection, the following warning is shown
> in the kernel log:
> 
>   [    0.574648] spi-nand spi0.0: GigaDevice SPI NAND was found.
>   [    0.635748] spi-nand spi0.0: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 128
>   [    0.649079] nand: WARNING: (null): the ECC used on your system is too weak compared to the one required by the NAND chip
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: spi-qpic-snand: validate user/chip specific ECC properties
      commit: 65cb56d49f6edea409600a3c61effc70ee5d43d8

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark