On 4/12/23 5:25 AM, Naresh Kamboju wrote: > On Wed, 12 Apr 2023 at 15:06, Naresh Kamboju <naresh.kamb...@linaro.org> > wrote: >> >> [sorry for the adding you in CC] >> >> While running LTP controllers test suite on this patch set applied on top of >> the next-20230406 and the following kernel panic noticed on qemu-i386. > > Also noticed on qemu-x86_64. > > Crash log link, > ------------------ > - > https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/lore_kernel_org_linux-block_20230404140835_25166-1-sergei_shtepa_veeam_com/testrun/16171908/suite/log-parser-test/test/check-kernel-panic/log > - > https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/build/lore_kernel_org_linux-block_20230404140835_25166-1-sergei_shtepa_veeam_com/testrun/16171908/suite/log-parser-test/tests/
Can you point me to the original report? I don't think my patches are the cause of the failure, or if they are there is a crazy bug. Above, I think you pointed me to the wrong link above because it looks like that's for a different patchset. Or did I misunderstand the testing and that link has my patches included? I did see my patches tested: https://qa-reports.linaro.org/~anders.roxell/linux-mainline-patches/ but they seem to fail in similar places as other failures that day, and the failures don't seem related to my patches. It doesn't look like you are doing anything nvme or block pr ioctl related and just failing on forks and OOM. It looks like you are booting from a scsi device but I only touched the scsi layer's code for persistent reservations and the tests don't seem to be using that code. > > lore link, > https://lore.kernel.org/linux-block/20230407200551.12660-1-michael.chris...@oracle.com/ > > > -- > Linaro LKFT > https://lkft.linaro.org -- dm-devel mailing list dm-devel@redhat.com https://listman.redhat.com/mailman/listinfo/dm-devel
