On 9/25/23 10:00, Bart Van Assche wrote: > On 9/24/23 21:47, Daisuke Matsuda (Fujitsu) wrote: >> As Bob wrote above, nobody has found any logical failure in rxe >> driver. > > That's wrong. In case you would not yet have noticed my latest email in > this thread, please take a look at > https://lore.kernel.org/linux-rdma/e8b76fae-780a-470e-8ec4-c6b650793d10@xxxxxxxxxxxxx/T/#m0fd8ea8a4cbc27b37b042ae4f8e9b024f1871a73. I think the report in that email is a 100% proof that there is a use-after-free issue in the rdma_rxe driver. Use-after-free issues have security implications and also can cause data corruption. I propose to revert the commit that introduced the rdma_rxe use-after-rpearson:src$ git clone git://git.kernel.org/pub/scm/linux/git/rafael/linux-pm Cloning into 'linux-pm'... fatal: remote error: access denied or repository not exported: /pub/scm/linux/git/rafael/linux-pm free unless someone comes up with a fix for the rdma_rxe driver. > > Bart. Bart, Having trouble following your recipe. The git repo you mention does not seem to be available. E.g. rpearson:src$ git clone git://git.kernel.org/pub/scm/linux/git/rafael/linux-pm Cloning into 'linux-pm'... fatal: remote error: access denied or repository not exported: /pub/scm/linux/git/rafael/linux-pm I am not sure how to obtain the tag if I cannot see the repo. If I just try to enable KASAN by setting CONFIG_KASAN=y in .config for the current linux-rdma repo and compile the kernel the kernel won't boot and is caught in some kind of SRSO hell. If I checkout Linus' v6.4 tag and add CONFIG_KASAN=y to a fresh .config file the kernel builds OK but when I try to boot it, it is unable to chroot to the root file system in boot. Any hints would be appreciated. Bob
