On Thu, Jan 28, 2021 at 02:34:45PM +0000, Christoph Lameter wrote: > On Thu, 28 Jan 2021, Jason Gunthorpe wrote: > > > I need patches to be sent in a way that shows in patchworks to be > > applied: > > > > https://patchwork.kernel.org/project/linux-rdma/list/ > > > I see it in patchworks: > > https://patchwork.kernel.org/project/linux-rdma/patch/alpine.DEB.2.22.394.2101251126090.344695@xxxxxxxxxxxxxxx/ It is not in the right format in patchwork, I get this mess when applying it: commit 9215f573b2ce9233b6d99d7b9b45bbcf3b2d9d90 (HEAD -> k.o/for-next) Author: Christoph Lameter <cl@xxxxxxxxx> Date: Mon Jan 25 11:28:57 2021 +0000 Fix: Remove racy Subnet Manager sendonly join checks On Sun, 24 Jan 2021, Leon Romanovsky wrote: > > Since all SMs out there have had support for sendonly join for years now > > we could just remove the check entirely. If there is an old grizzly SM out > > there then it would not process that join request and would return an > > error. > > I have no idea if it possible, if yes, this will be the best solution. Ok hier ist ein neuer Patch: From: Christoph Lameter <cl@xxxxxxxxx> Subject: [PATCH] Fix: Remove racy Subnet Manager sendonly join checks When a system receives a REREG event from the SM, then the SM information in the kernel is marked as invalid and a request is sent to the SM to update the information. The SM information is invalid in that time period. However, receiving a REREG also occurs simultaneously in user space applications that are now trying to rejoin the multicast groups. Some of those may be sendonly multicast groups which are then failing. If the SM information is invalid then ib_sa_sendonly_fullmem_support() returns false. That is wrong because it just means that we do not know yet if the potentially new SM supports sendonly joins. Sendonly join was introduced in 2015 and all the Subnet managers have supported it ever since. So there is no point in checking if a subnet manager supports it. Should an old opensm get a request for a sendonly join then the request will fail. The code that is removed here accomodated that situation and fell back to a full join. Falling back to a full join is problematic in itself. The reason to use the sendonly join was to reduce the traffic on the Infiniband fabric otherwise one could have just stayed with the regular join. So this patch may cause users of very old opensms to discover that lots of traffic needlessly crosses their IB fabrics. Signed-off-by: Christoph Lameter <cl@xxxxxxxxx> Link: https://lore.kernel.org/r/alpine.DEB.2.22.394.2101251126090.344695@xxxxxxxxxxxxxxx Signed-off-by: Jason Gunthorpe <jgg@xxxxxxxxxx> > > > Index: linux/drivers/infiniband/core/cma.c > > > =================================================================== > > > +++ linux/drivers/infiniband/core/cma.c 2021-01-25 09:39:29.191032891 +0000 > > > @@ -4542,17 +4542,6 @@ static int cma_join_ib_multicast(struct > > > > Also if patches aren't generated with 'git diff' then I won't fix any > > minor conflicts :( > > Well it was quilt ...... Do I need to put it into a git tree somewhere? If you are doing this a lot get a quilt that can generate git diff format output. https://lists.gnu.org/archive/html/quilt-dev/2015-06/msg00002.html Jason
