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: tipc-discussion@lists.sourceforge.n
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&id=c57e51ffd1d910d595ccb3af3ae70eeeb6d423a2
Mar 23 15:13:25 [SEQ 429763] kernel: [ 8289.000919] Workqueue:
tipc_rcv tipc_rec
I am using kernel 4.4.0 and have seen following panic. Please let me
know if fix is available for this issue?
[67670.162758] BUG: unable to handle kernel NULL pointer dereference
at 0039
[67670.170664] IP: [] __tipc_sendmsg+0x1be/0x5a0 [tipc]
[67670.177231] PGD 34de24067 PUD 3505f5067
Happens in both 4.2.0 and 4.5.0 kernels too
-Original Message-
From: Rune Torgersen [mailto:ru...@innovsys.com]
Sent: Wednesday, March 23, 2016 9:26 AM
To: tipc-discussion@lists.sourceforge.net
Subject: Re: [tipc-discussion] TIPC nametable NULL ptr kernel crash
Could this be caused by us
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 To
Hi,
That is the one. However, I see in a different mail from Rune Torgersen that
the problem might still be there, despite the fix.
Just try 4.5.0 and see if you get the same problem.
Regards
///jon
> -Original Message-
> From: GUNA [mailto:gbala...@gmail.com]
> Sent: Thursday, 24 March
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 fu
Ok. I'm going to try an older kernel (3.14.1) to see if that works for us until
a fix is found.
-Original Message-
From: Jon Maloy [mailto:jon.ma...@ericsson.com]
Sent: Thursday, March 24, 2016 1:56 PM
To: Rune Torgersen; tipc-discussion@lists.sourceforge.net
Subject: RE: [tipc-discussi
I could not able to move 4.5.0 but I could merge all the following tipc
changes in 4.5.0 (except merge git). If I need to pickup any other fixes
please let me know.
Also, I do see there are discussions about "Dropping name table update ..."
issue but don't see any solution. If there is a solution
Regarding "Dropping name table" ...
It seems working if TIPC_ZONE_SCOPE is replaced by TIPC_CLUSTER_ZONE.
Could you let me know where the change should be applied (ie:file/function)?
On Thu, Mar 24, 2016 at 3:28 PM, GUNA wrote:
> I could not able to move 4.5.0 but I could merge all the following
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: Thursday
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] t
12 matches
Mail list logo
