On Wed, 10 May 2023 09:42:23 +0200, Loic Poulain wrote:
> User should not be able to write block device if it is read-only at
> block level (e.g force_ro attribute). This is ensured in the regular
> fops write operation (blkdev_write_iter) but not when writing via
> user mapping (mmap), allowing user to actually write a read-only
> block device via a PROT_WRITE mapping.
>
> Example: This can lead to integrity issue of eMMC boot partition
> (e.g mmcblk0boot0) which is read-only by default.
>
> [...]
Applied, thanks!
[1/1] block: Deny writable memory mapping if block is read-only
commit: 69baa3a623fd2e58624f24f2f23d46f87b817c93
Best regards,
--
Jens Axboe
