summaryrefslogtreecommitdiffstats
path: root/io_uring/register.c
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2024-04-05 16:30:04 +0200
committerMiquel Raynal <miquel.raynal@bootlin.com>2024-04-09 08:38:41 +0200
commit21c9fb611c25d5cd038f6fe485232e7884bb0b3d (patch)
treedae3b4c3fa03c295f3e321d3bbe20c552602c652 /io_uring/register.c
parentb61bb5bc2c1cd00bb53db42f705735db6e8700f0 (diff)
downloadlinux-stable-21c9fb611c25d5cd038f6fe485232e7884bb0b3d.tar.gz
linux-stable-21c9fb611c25d5cd038f6fe485232e7884bb0b3d.tar.bz2
linux-stable-21c9fb611c25d5cd038f6fe485232e7884bb0b3d.zip
mtd: diskonchip: work around ubsan link failure
I ran into a randconfig build failure with UBSAN using gcc-13.2: arm-linux-gnueabi-ld: error: unplaced orphan section `.bss..Lubsan_data31' from `drivers/mtd/nand/raw/diskonchip.o' I'm not entirely sure what is going on here, but I suspect this has something to do with the check for the end of the doc_locations[] array that contains an (unsigned long)0xffffffff element, which is compared against the signed (int)0xffffffff. If this is the case, we should get a runtime check for undefined behavior, but we instead get an unexpected build-time error. I would have expected this to work fine on 32-bit architectures despite the signed integer overflow, though on 64-bit architectures this likely won't ever work. Changing the contition to instead check for the size of the array makes the code safe everywhere and avoids the ubsan check that leads to the link error. The loop code goes back to before 2.6.12. Cc: stable@vger.kernel.org Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Link: https://lore.kernel.org/linux-mtd/20240405143015.717429-1-arnd@kernel.org
Diffstat (limited to 'io_uring/register.c')
0 files changed, 0 insertions, 0 deletions