On Wed, Mar 17, 2021 at 04:56:15PM +0530, Naresh Kamboju wrote: > On Wed, 17 Mar 2021 at 15:34, Greg Kroah-Hartman > <gre...@linuxfoundation.org> wrote: > > > > On Wed, Mar 17, 2021 at 02:28:40PM +0530, Naresh Kamboju wrote: > > > While booting Linux mainline master 5.12.0-rc2 and 5.12.0-rc3 on arm64 > > > Hikey device the following KFENCE bug was found. > > > > > > Recently, we have enabled CONFIG_KFENCE=y and started seeing this crash. > > > kernel BUG log: > > > > What USB traffic are you having here? > > This is getting triggered while booting the device. > We are not running any traffic.
Ah, so this is device probe time. > > And has this ever not triggered? > > No. > It was not triggered before. > Since CONFIG_KFENCE=y is added to our builds recently we are able to > reproduce always on recent builds. > > Steps to reproduce: > 1) Build arm64 kernel Image with this given config. > - tuxmake --runtime podman --target-arch arm64 --toolchain gcc-9 > --kconfig defconfig --kconfig-add > https://builds.tuxbuild.com/1pfztfszUNcDwOAyMrw2wPMKNfc/config > 2) Boot arm64 hikey hi6220 device > 3) While booting the device you will get to see this kernel BUG: > > [ 18.243075] BUG: KFENCE: memory corruption in > usb_get_device_descriptor+0x80/0xb0 > [ 18.813861] BUG: KFENCE: memory corruption in > __usbnet_read_cmd.isra.0+0xd0/0x1a0 There was a warning before this, from the hub code, when reading from this device as well. Perhaps this is just a side affect of the real memory corruption issue somewhere else? Bisection would be nice, but I'm placing odds on this always being an issue here in this driver code... thanks for the report. greg k-h
