Thanks Mark for the clarification.
Dheeraj
On Fri, Oct 25, 2019 at 12:15 PM Mark Johnston wrote:
> On Fri, Oct 25, 2019 at 11:36:53AM -0400, Dheeraj Kandula wrote:
> > Hi Mark,
> >I am trying to understand the purpose of certain code in
> > soisconnected.
>
>
On Fri, Oct 25, 2019 at 11:36:53AM -0400, Dheeraj Kandula wrote:
> Hi Mark,
>I am trying to understand the purpose of certain code in
> soisconnected.
+freebsd-net
> 1. When an upcall returns SO_ISCONNECTED, the sockbuf's lock is unlocked
> and then soisconnected is i
On Tue, 13 Jun 2006, Blue wrote:
I have found a questionable code in soisconnected() function in
uipc_socket2.c. In the very beginning, the SOCK_LOCK() would lock the
socket. However, in line 127, it unlocks socket. I am wondering that
SOCK_UNLOCK() should be called until all the socket
Hi,all:
I have found a questionable code in soisconnected() function in
uipc_socket2.c. In the very beginning, the SOCK_LOCK() would lock the
socket. However, in line 127, it unlocks socket. I am wondering that
SOCK_UNLOCK() should be called until all the socket's parameters are
done.
Jon wrote:
>
> I am reading 'soisconnected' function in 'Uipc_socket2.c' file.
> I find this lines. But I cannot find accf's mean. can you explain to me?thank
> you very much!
This is the accept filter stuff we have. Take a look at setsockopt(2)
and accep
I am reading 'soisconnected' function in 'Uipc_socket2.c' file.
I find this lines. But I cannot find accf's mean. can you explain to me?thank
you very much!
if ((so->so_options & SO_ACCEPTFILTER) == 0) {
...
} else {
ACCEPT_UNLOCK();
SOCK_LOCK(so)