linux-kernel - Re: [PATCH v3] spi: intel: Allow writeable MTD partition with module param

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: <175346140458.1149754.12210062974828341845.b4-ty@kernel.org>
Date: Fri, 25 Jul 2025 17:36:44 +0100
From: Mark Brown <broonie@...nel.org>
To: Jakub Czapiga <czapiga@...gle.com>
Cc: Mika Westerberg <mika.westerberg@...ux.intel.com>, 
 Konrad Adamczyk <konrada@...gle.com>, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] spi: intel: Allow writeable MTD partition with
 module param

On Fri, 25 Jul 2025 12:25:42 +0000, Jakub Czapiga wrote:
> The MTD device is blocked from writing to the SPI-NOR chip if any region
> of it is write-protected, even if "writeable=1" module parameter is set.
> 
> Add ability to bypass this behaviour by introducing new module parameter
> "ignore_protestion_status" which allows to rely on the write protection
> mechanism of SPI-NOR chip itself, which most modern chips (since
> the 1990'+) have already implemented.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: intel: Allow writeable MTD partition with module param
      commit: 87aa3c8d8c4aa2e2567fe04126d14eb9fde815e5

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