> TCP without net ns notifier missed the net ns delete scenario results in a use after free bug, that should be fixed first as its critical. > > Sure. I also confronted this mentioned problem. If I remember correctly, > a net ns callback can fix this problem. I'm not sure if the bug fix will be this in depth, but I have a related question. What is the proper way for the kernel nvme initiator code to know which netns context to use? e.g. should we take the pid of the process that opened /dev/nvme-fabrics and look it up (presumaly this will be nvme-cli), and will this method give us enough details for both tcp & rdma? Mark On Tue, Apr 18, 2023 at 10:19 PM Zhu Yanjun <yanjun.zhu@xxxxxxxxx> wrote: > > > 在 2023/4/19 8:43, Parav Pandit 写道: > > > >> From: Mark Lehrer <lehrer@xxxxxxxxx> > >> Sent: Friday, April 14, 2023 12:24 PM > > > >> I'm going to try making the nvme-fabrics set of modules use the network > >> namespace properly with RoCEv2. TCP seems to work properly already, so this > >> should be more of a "port" than real development. > > TCP without net ns notifier missed the net ns delete scenario results in a use after free bug, that should be fixed first as its critical. > > Sure. I also confronted this mentioned problem. If I remember correctly, > a net ns callback can fix this problem. > > Zhu Yanjun > > > > >> Are you (or anyone else) interested in working on this too? I'm more familiar > >> with the video frame buffer area of the kernel, so first I'm familiarizing myself > >> with how nvme-fabrics works with TCP & netns. > >> > >> Thanks, > >> Mark
