Re: [PATCH 4/6] sock: Introduce the SO_PEEK_OFF sock option
From: David Miller <davem@davemloft.net>
Date: 2012-02-21 20:05:37
From: Eric Dumazet <redacted> Date: Tue, 21 Feb 2012 18:45:50 +0100
Le mardi 21 février 2012 à 21:31 +0400, Pavel Emelyanov a écrit :quoted
This one specifies where to start MSG_PEEK-ing queue data from. When set to negative value means that MSG_PEEK works as ususally -- peeks from the head of the queue always. When some bytes are peeked from queue and the peeking offset is non negative it is moved forward so that the next peek will return next portion of data. When non-peeking recvmsg occurs and the peeking offset is non negative is is moved backward so that the next peek will still peek the proper data (i.e. the one that would have been picked if there were no non peeking recv in between). The offset is set using per-proto opteration to let the protocol handle the locking issues and to check whether the peeking offset feature is supported by the protocol the socket belongs to. Signed-off-by: Pavel Emelyanov <redacted>
...
small note : should be moved down by one line, after SCM_WIFI_STATUS Other than that,
You also didn't update all of the arch/*/include/asm/socket.h files. I took care of all of this, but what should have been a simple matter of me typing "git am --signoff foo.mbox" and "make" turned into a 10 minute exercise in raking leaves. :-/