mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ying Xue <ying.xue@windriver.com>
To: Jon Maloy <jon.maloy@ericsson.com>,
	Mihai Moldovan <ionic@ionic.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Userspace woes with 5.1.5 due to TIPC
Date: Fri, 31 May 2019 19:13:43 +0800	[thread overview]
Message-ID: <5498070b-c6e4-30e5-dea4-5767fe50f617@windriver.com> (raw)
In-Reply-To: <CH2PR15MB3575E1402F1FF4418C8C67139A190@CH2PR15MB3575.namprd15.prod.outlook.com>

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

      reply	other threads:[~2019-05-31 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 19:33 Mihai Moldovan
2019-05-30 19:51 ` Jon Maloy
2019-05-30 20:47   ` Mihai Moldovan
2019-05-31  0:41     ` Ying Xue
2019-05-31 11:02       ` Jon Maloy
2019-05-31 11:13         ` Ying Xue [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5498070b-c6e4-30e5-dea4-5767fe50f617@windriver.com \
    --to=ying.xue@windriver.com \
    --cc=ionic@ionic.de \
    --cc=jon.maloy@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®