mirror of
https://passt.top/passt
synced 2024-09-19 14:00:53 +00:00
a09aeb4bd6
When using the new SO_PEEK_OFF feature on TCP sockets, we must adjust
the SO_PEEK_OFF value whenever we move conn->seq_to_tap backwards.
Although it was discussed during development, somewhere during the shuffles
the case where we move the pointer backwards because we lost frames while
sending them to the guest. This can happen, for example, if the socket
buffer on the Unix socket to qemu overflows.
Fixing this is slightly complicated because we need to pass a non-const
context pointer to some places we previously didn't need it. While we're
there also fix a small stylistic issue in the function comment for
tcp_revert_seq() - it was using spaces instead of tabs.
Fixes: e63d281871 ("tcp: leverage support of SO_PEEK_OFF socket option when available")
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Reviewed-by: Stefano Brivio <sbrivio@redhat.com>
17 lines
513 B
C
17 lines
513 B
C
/* SPDX-License-Identifier: GPL-2.0-or-later
|
|
* Copyright (c) 2021 Red Hat GmbH
|
|
* Author: Stefano Brivio <sbrivio@redhat.com>
|
|
*/
|
|
|
|
#ifndef TCP_BUF_H
|
|
#define TCP_BUF_H
|
|
|
|
void tcp_sock4_iov_init(const struct ctx *c);
|
|
void tcp_sock6_iov_init(const struct ctx *c);
|
|
void tcp_flags_flush(const struct ctx *c);
|
|
void tcp_payload_flush(struct ctx *c);
|
|
int tcp_buf_data_from_sock(struct ctx *c, struct tcp_tap_conn *conn);
|
|
int tcp_buf_send_flag(struct ctx *c, struct tcp_tap_conn *conn, int flags);
|
|
|
|
#endif /*TCP_BUF_H */
|