Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp466785ybi; Fri, 31 May 2019 04:25:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqw/Lb4lmuj9jszBqY/RvgKzQdt6SkITT4lU2lHihwE7maWmTP8E60GZb+oeh5/+f+XNa5N3 X-Received: by 2002:a17:90a:8c90:: with SMTP id b16mr8714162pjo.85.1559301931513; Fri, 31 May 2019 04:25:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559301931; cv=none; d=google.com; s=arc-20160816; b=Z/ujGJBUbc/plX8gCPd6LpK/KrwSOayUAeZju1JZFcuzLGNinlzvZPYMGoFNyC0rd6 I2vwdjgX1lUChVyoc9CzRvUK/Qhdw1Sshads3HgmIOSGLTq/YMGu0EhP36ZOT5O4Fv6O 9j1aWhyrkybG+JXEu5zP5YEyFBZnqmefi8OAhludl1n7XQAo7wvXsUXdsikLjCtbxSOT ji5RNt08Ek6rva3fhZzIDNSM+gFpG4xhsYvEFsCjtTsGCAWdaSKtGTmCX216iPz1+BBV 0SqTuIoQjGxv1CTFsv6oOV3WNNibYKU7+1fIZas0S15SvPt8ir6Z5mSZyms4oR06IDRy 3orQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject; bh=qnWTcZJlgC00jYRgurH0Q/nLOmbEr5HiuMcF4EDYitg=; b=tt2Fq1tikONwORjvPFqQx5vMaLs6DWquOO1s4Zw4h45rS8uY3CZeFXrUnk/fQPZO9n wpTH2+nv0MCS64TVeHxTS4WGmu17gry0ZZoHtLJe8AGoJ5lpytBfhBrZtXfA9pUUF4fk qsP+4vWEcBwtYcpKtMxskd+TTkMaFnytIHxVYugskACx1CEjyy4EI9TcKDE+mwT5fDv8 77FwlaEXLWNpCmD6ppqWt1hbjmnsCydrUYJN78ZeJqKM3ZtCjVhnLX84i4sKi3BpTANV v70ZAGNNC5XalPk0HIHuNgWT8/MWoo9pHWWPFfCjeeOXYhqWQzccY0N0ielmsH3ECOEc 0G7w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w14si885358pfn.105.2019.05.31.04.25.13; Fri, 31 May 2019 04:25:31 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727151AbfEaLXu (ORCPT + 99 others); Fri, 31 May 2019 07:23:50 -0400 Received: from mail1.windriver.com ([147.11.146.13]:64077 "EHLO mail1.windriver.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726158AbfEaLXu (ORCPT ); Fri, 31 May 2019 07:23:50 -0400 Received: from ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) by mail1.windriver.com (8.15.2/8.15.1) with ESMTPS id x4VBNZNC029641 (version=TLSv1 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 31 May 2019 04:23:35 -0700 (PDT) Received: from [128.224.155.90] (128.224.155.90) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.3.439.0; Fri, 31 May 2019 04:23:34 -0700 Subject: Re: Userspace woes with 5.1.5 due to TIPC To: Jon Maloy , Mihai Moldovan , "linux-kernel@vger.kernel.org" References: <4ad776cb-c597-da1d-7d5e-af39ded17c40@ionic.de> <1780dd6a-9546-0df5-7fb2-44b78643b079@ionic.de> <3cc60b11-2b63-3bfc-2be8-569f2b0ce7cf@windriver.com> From: Ying Xue Message-ID: <5498070b-c6e4-30e5-dea4-5767fe50f617@windriver.com> Date: Fri, 31 May 2019 19:13:43 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [128.224.155.90] Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 5/31/19 7:02 PM, Jon Maloy wrote: > This was the very reason the broken patch was introduced. AFAIK there is no problem after the corrected version of that patch was applied. I have prepared for our patches on net-next tree. But when I checked my patches on net tree, it's found that the issue has been fixed with commit 526f5b851a96566803ee4bee60d0a34df56c77f8 ("tipc: fix modprobe tipc failed after switch order of device registration"). There are four commits which were introduced recently, and their names are quite similar, and the fix is not merged into net-next tree, which makes me misunderstood the issue status. Anyway, it looks like failing to insert TIPC module has been resolved. But I have not validated the fix by create multiple TIPC namespace, so I am not sure whether it works normally. Thanks, Ying