FAILED: patch "[PATCH] mtd: spi-nor: Fix shift-out-of-bounds in" failed to apply to 5.4-stable tree
Subsystems (3)
[email protected]
maintainerThe patch below does not apply to the 5.4-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
To reproduce the conflict and resubmit, you may use the following commands:
git fetch https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ linux-5.4.y
git checkout FETCH_HEAD
git cherry-pick -x f0f0cfdc3a024e21161714f2e05f0df3b84d42ad
# <resolve conflicts, build, test, etc.>
git commit -s
git send-email --to '<[email protected]>' --in-reply-to '[email protected]' --subject-prefix 'PATCH 5.4.y' HEAD^..
Possible dependencies:
f0f0cfdc3a02 ("mtd: spi-nor: Fix shift-out-of-bounds in spi_nor_set_erase_type") cb481b92d10f ("mtd: spi-nor: Move SFDP logic out of the core") a0900d0195d2 ("mtd: spi-nor: Prepare core / manufacturer code split") 69228a0224c5 ("Merge tag 'mtk-mtd-spi-move' into spi-nor/next")
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From f0f0cfdc3a024e21161714f2e05f0df3b84d42ad Mon Sep 17 00:00:00 2001
From: Louis Rannou <[email protected]>
Date: Fri, 3 Feb 2023 09:07:54 +0200
Subject: [PATCH] mtd: spi-nor: Fix shift-out-of-bounds in
spi_nor_set_erase_type
spi_nor_set_erase_type() was used either to set or to mask out an erase type. When we used it to mask out an erase type a shift-out-of-bounds was hit:
UBSAN: shift-out-of-bounds in drivers/mtd/spi-nor/core.c:2237:24
shift exponent 4294967295 is too large for 32-bit type 'int'
The setting of the size_{shift, mask} and of the opcode are unnecessary when the erase size is zero, as throughout the code just the erase size is considered to determine whether an erase type is supported or not. Setting the opcode to 0xFF was wrong too as nobody guarantees that 0xFF is an unused opcode. Thus when masking out an erase type, just set the erase size to zero. This will fix the shift-out-of-bounds.
drivers/mtd/spi-nor/core.c +9 -0
@@ -2026,6 +2026,15 @@ void spi_nor_set_erase_type(struct spi_nor_erase_type *erase, u32 size, erase->size_mask = (1 << erase->size_shift) -1 ; } +/** +* spi_nor_mask_erase_type() - mask out a SPI NOR erase type +* @erase: pointer to a structure that describes a SPI NOR erase type +*/ +void spi_nor_mask_erase_type (struct spi_nor_erase_type *erase) +{ + erase->size =0 ; +} +/** * spi_nor_init_uniform_erase_map() - Initialize uniform erase map * @map: the erase map of the SPI NOR
drivers/mtd/spi-nor/core.h +1 -0
@@ -681,6 +681,7 @@ void spi_nor_set_pp_settings(struct spi_nor_pp_command *pp, u8 opcode,void spi_nor_set_erase_type (struct spi_nor_erase_type *erase,u32 size,u8 opcode); +void spi_nor_mask_erase_type (struct spi_nor_erase_type *erase);struct spi_nor_erase_region *spi_nor_region_next (struct spi_nor_erase_region *region); void spi_nor_init_uniform_erase_map(struct spi_nor_erase_map *map,
drivers/mtd/spi-nor/sfdp.c +2 -2
@@ -875,7 +875,7 @@ static int spi_nor_init_non_uniform_erase_map(struct spi_nor *nor,*/ for (i =0 ; i <SNOR_ERASE_TYPE_MAX ; i++)if (!(regions_erase_type &BIT (erase[i].idx))) -spi_nor_set_erase_type (&erase[i],0 ,0xFF ); +spi_nor_mask_erase_type (&erase[i]);return 0 ; }
@@ -1089,7 +1089,7 @@ static int spi_nor_parse_4bait(struct spi_nor *nor, erase_type[i].opcode = (dwords[SFDP_DWORD (2 )] >> erase_type[i].idx *8 ) &0xFF ; else - spi_nor_set_erase_type(&erase_type[i], 0u, 0xFF); + spi_nor_mask_erase_type(&erase_type[i]); }/*