It looks to me from my dmesg dump that I'm actually crashing on line 285 in
subscr.c.
From: Jon Maloy [jon.ma...@ericsson.com]
Sent: Thursday, March 24, 2016 1:56 PM
To: Rune Torgersen; tipc-discussion@lists.sourceforge.net
Subject: RE: [tipc-discussion]
No, that turned out to not matter.
In my case, upgrading to 4.5.0 (or down to 3.14.1 or 4.2.0) seemed to fix it.
Anyways, it is the scope field in the sockaddr_tipc class when passed to bind()
on a receive socket.
-Original Message-
From: GUNA [mailto:gbala...@gmail.com]
Sent:
Hi,
This is not a known problem. Looking at the dump and the code it may
look as if somebody is sending in a TIPC_ADDR_NAMEd message with a zero
sockaddr pointer.
This should of course not lead to a kernel crash, but it might still
give a hint of what is triggering the problem, so you can get
Hi Rune,
As far as I can see the fix is present in the 4.5.0 code (subscr.c, line 299),
so it may be that there still is a problem.
I suspect you will have to wait until Partha is back from Easter leave to get a
better answer to this.
Regards
///jon
> -Original Message-
> From: Rune
Please confirm the following will fix the issue reported below:
// fix in 4.4.4
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.4.y=c57e51ffd1d910d595ccb3af3ae70eeeb6d423a2
Mar 23 15:13:25 [SEQ 429763] kernel: [ 8289.000919] Workqueue:
tipc_rcv
4.5.0 kernel still gets a NULL ptr. I have kernel core dumps if anyone knows
what to look for.
I am now trying 4.2 kernel.
-Original Message-
From: Rune Torgersen [mailto:ru...@innovsys.com]
Sent: Wednesday, March 23, 2016 12:48 PM
To: 'Erik Hugne'
Cc:
