search for: virtio_vsock_skb_rx_put

...I would use the same to avoid confusion. Plus that's the >> value the other peer sent us, so definitely the right value to increase >> fwd_cnt with. But if skb->len always reflects it, then that's fine. >i've checked 'virtio_transport_rx_work()', it calls 'virtio_vsock_skb_rx_put()' which >sets 'skb->len'. Value is used from header, so seems 'skb->len' == 'hdr->len' in this >case. Thank you for checking it. However, I still think it is better to use `hdr->len` (we have to assign it to `pkt_len` anyway, as in the proposal I se...

...gt;tap_delivered = false; > } > >+static inline bool virtio_vsock_skb_has_frags(struct sk_buff *skb) >+{ >+ if (!skb_is_nonlinear(skb)) >+ return false; >+ >+ return VIRTIO_VSOCK_SKB_CB(skb)->curr_frag != skb_shinfo(skb)->nr_frags; >+} >+ > static inline void virtio_vsock_skb_rx_put(struct sk_buff *skb) > { > u32 len; >-- >2.25.1