From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 27426C04AB6 for ; Fri, 31 May 2019 11:23:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F1BDF2682D for ; Fri, 31 May 2019 11:23:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727187AbfEaLXu (ORCPT ); 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