Displaying 3 results from an estimated 3 matches for "tcp_sendmsg_lock".
Did you mean:
tcp_sendmsg_locked
2023 Aug 31
0
[RFC PATCH v2 0/2] vsock: handle writes to shutdowned socket
...ocket which was shutdowned with 'shutdown()' (both sides - local with
>SHUT_WR flag, peer - with SHUT_RD flag). According POSIX we must send
>SIGPIPE in such cases (but SIGPIPE is not send when MSG_NOSIGNAL is set).
>
>First patch is implemented in the same way as net/ipv4/tcp.c:tcp_sendmsg_locked().
>It uses 'sk_stream_error()' function which handles EPIPE error. Another
>way is to use code from net/unix/af_unix.c:unix_stream_sendmsg() where
>same logic from 'sk_stream_error()' is implemented "from scratch", but
>it doesn't check 'sk_err'...
2023 Jun 17
2
[PATCH net-next v2 17/17] net: Kill MSG_SENDPAGE_NOTLAST
Now that ->sendpage() has been removed, MSG_SENDPAGE_NOTLAST can be cleaned
up. Things were converted to use MSG_MORE instead, but the protocol
sendpage stubs still convert MSG_SENDPAGE_NOTLAST to MSG_MORE, which is now
unnecessary.
Signed-off-by: David Howells <dhowells at redhat.com>
cc: "David S. Miller" <davem at davemloft.net>
cc: Eric Dumazet <edumazet at
2017 Dec 18
0
KASAN: double-free or invalid-free in skb_free_head
...v4/ip_output.c:124
ip_queue_xmit+0x8c6/0x18e0 net/ipv4/ip_output.c:504
tcp_transmit_skb+0x1b12/0x38b0 net/ipv4/tcp_output.c:1176
tcp_write_xmit+0x680/0x5190 net/ipv4/tcp_output.c:2367
__tcp_push_pending_frames+0xa0/0x250 net/ipv4/tcp_output.c:2543
tcp_push+0x538/0x770 net/ipv4/tcp.c:730
tcp_sendmsg_locked+0x2663/0x3b30 net/ipv4/tcp.c:1424
tcp_sendmsg+0x2f/0x50 net/ipv4/tcp.c:1461
inet_sendmsg+0x11f/0x5e0 net/ipv4/af_inet.c:763
sock_sendmsg_nosec net/socket.c:636 [inline]
sock_sendmsg+0xca/0x110 net/socket.c:646
sock_write_iter+0x31a/0x5d0 net/socket.c:915
call_write_iter include/linux/...