[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61563ebaf2fe0_6c4e420813@john-XPS-13-9370.notmuch>
Date: Thu, 30 Sep 2021 15:48:26 -0700
From: John Fastabend <john.fastabend@...il.com>
To: Liu Jian <liujian56@...wei.com>, john.fastabend@...il.com,
daniel@...earbox.net, jakub@...udflare.com, lmb@...udflare.com,
davem@...emloft.net, kuba@...nel.org, ast@...nel.org,
andrii@...nel.org, kafai@...com, songliubraving@...com, yhs@...com,
kpsingh@...nel.org, netdev@...r.kernel.org, bpf@...r.kernel.org,
xiyou.wangcong@...il.com
Cc: liujian56@...wei.com
Subject: RE: [PATCH v4] skmsg: lose offset info in sk_psock_skb_ingress
Liu Jian wrote:
> If sockmap enable strparser, there are lose offset info in
> sk_psock_skb_ingress. If the length determined by parse_msg function
> is not skb->len, the skb will be converted to sk_msg multiple times,
> and userspace app will get the data multiple times.
>
> Fix this by get the offset and length from strp_msg.
> And as Cong suggestion, add one bit in skb->_sk_redir to distinguish
> enable or disable strparser.
>
> Signed-off-by: Liu Jian <liujian56@...wei.com>
> ---
Thanks. Please add Fixes tags so we can track these I've added it here.
This has been broken from the initial patches and after a quick glance I
suspect this will need manual backports if we need it. Also all the
I use and all the selftests set parser to a nop by returning skb->len.
Can you also create a test so we can ensure we don't break this
again?
Fixes: 604326b41a6fb ("bpf, sockmap: convert to generic sk_msg interface")
Acked-by: John Fastabend <john.fastabend@...il.com>
Powered by blists - more mailing lists