From: Erik Hugne [mailto:erik.hu...@gmail.com]
Sent: Monday, 30 May, 2016 07:08
To: Jon Maloy
Cc: Jon Maloy; Ying Xue; GUNA; Xue Ying (ying.x...@gmail.com);
tipc-discussion@lists.sourceforge.net
Subject: RE: [tipc-discussion] tipc_sk_rcv: Kernel panic on one of the card on
4.4.0
oops, hit "se
Hi Jon,
First of all, slock lock is designed very specially and wisely. In process
context, it's similar to a mutex. By contrast, in interrupt context, it likes a
spin lock. Moreover, it can safely protect members of sock struct on both
contexts. When we are in interrupt/softirq mode and the "o
> -Original Message-
> From: Xue, Ying [mailto:ying@windriver.com]
> Sent: Monday, 30 May, 2016 14:15
> To: Jon Maloy; GUNA; Jon Maloy; tipc-discussion@lists.sourceforge.net; Erik
> Hugne; Xue Ying (ying.x...@gmail.com)
> Subject: RE: [tipc-discussion] tipc_sk_rcv: Kernel panic on one
This is just RFC for now, i have not tested it.
Following the example of tcp_write_timer, should the socket be owned
by user when the timer expires, we defer the processing to a release
callback which will be invoked when release_sock is called.
Signed-off-by: Erik Hugne
---
net/tipc/socket.c |
