Received: by 2002:a05:6358:111d:b0:dc:6189:e246 with SMTP id f29csp2283369rwi; Thu, 3 Nov 2022 15:12:38 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4DMOJlgYy/HveCJU+8aZmt88IJXCw4xp4EnrlmHjLlqt3D1dyi8HHzeXqsIFgk2I9xkvBk X-Received: by 2002:a17:906:fe46:b0:73d:939a:ec99 with SMTP id wz6-20020a170906fe4600b0073d939aec99mr31582569ejb.169.1667513558746; Thu, 03 Nov 2022 15:12:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667513558; cv=none; d=google.com; s=arc-20160816; b=AT0f11KpQlFXnYoSb63DgqWSkQt5ockMdv6kv7QTJqk7cftP9eoaY4rwBNIUo56F9P +A8oLVGHsqCjhHV14MuHmgszD8fh0OmFvUU+N86BcyFZtns+vHKKDg5qs3n+yEvGbuku lO+g+UQO7wyBz/FLBEl+5DLF5falqfpH2xipwikNWZOMcQDZt4U6awZC8f6rAibioUMH 1s8TEa6aH0Q+0P7OK+UgaO6rMZTfHv7LEn30XSD45nnSVeJhdO3Rz8bVCsTXFoG2SK5n kNygDWyT0Wd0tSNs5IbDUZBkPx8rleiFC7sXvMJG12Ij8tKmPVxA7aRhS37JBc0IkvTP bTQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :content-language:references:cc:to:subject:mime-version:date :dkim-signature:message-id; bh=hQcKEXuHs/7YZtQkNBeKwRLPigLlS9nAKVIGEHzvGaU=; b=m89rrkKY2C1hvihE65SycUq/mYUAC0cZw7G7MJXOT3wD5BMj7WjWXRWSw1hz6yWXNu 4sxo7fzIJdbaKUtUQMdierMH3fN2iBCp0KZk612hA3n40Y2E0qDCYD7TZtPjo5Z3Oe6S ERw5U0+gyVUb4K4Ou8Qnsy74N/uf5J9zBX2kDUpPNGO3Y+byZzEC4hCm7SDFWHabWw/a d77Vm+VtFgQJytpSrjUO7EqyJ8PG0be2tHLxrL/0Er/XqtewZLgoXWqP+hhqcnejRjKO 4THEz2nDRW0Tt7JQXOFyJEed8RSkVAzfaflPzh0gVOW8buXbbhLegqCGs0/45HBl5IXl 7R6w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b="Yxm3Oq/Y"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id u22-20020aa7d0d6000000b00461b0b4f1afsi2420749edo.288.2022.11.03.15.12.13; Thu, 03 Nov 2022 15:12:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linux.dev header.s=key1 header.b="Yxm3Oq/Y"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linux.dev Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231566AbiKCVKd (ORCPT + 98 others); Thu, 3 Nov 2022 17:10:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33782 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231391AbiKCVKA (ORCPT ); Thu, 3 Nov 2022 17:10:00 -0400 Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AF80613F4A; Thu, 3 Nov 2022 14:08:28 -0700 (PDT) Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1667509674; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=hQcKEXuHs/7YZtQkNBeKwRLPigLlS9nAKVIGEHzvGaU=; b=Yxm3Oq/Y7WeBDzWz4L8zz22I/FsSLUnL28y2NM6dbdseg9ViJ6gWVDMHi0aYwH5LcwpTY7 OycpSxUV32zu00hDdWahU3vjG6u9Yj+ZPMmjlaxX/l7GKJicQTJkcVUXCcr8UhQG7VC5aq /cYzQWWrwbLN3iA5Yvs78xVGcouNVhM= Date: Thu, 3 Nov 2022 14:07:44 -0700 MIME-Version: 1.0 Subject: Re: [PATCH v4,bpf-next] bpf: Don't redirect packets with invalid pkt_len To: Zhengchao Shao Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org, song@kernel.org, yhs@fb.com, john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com, bigeasy@linutronix.de, imagedong@tencent.com, petrm@nvidia.com, arnd@arndb.de, dsahern@kernel.org, talalahmad@google.com, keescook@chromium.org, haoluo@google.com, jolsa@kernel.org, weiyongjun1@huawei.com, yuehaibing@huawei.com, bpf@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, hawk@kernel.org References: <20220715115559.139691-1-shaozhengchao@huawei.com> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Martin KaFai Lau In-Reply-To: <20220715115559.139691-1-shaozhengchao@huawei.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/15/22 4:55 AM, Zhengchao Shao wrote: > Syzbot found an issue [1]: fq_codel_drop() try to drop a flow whitout any > skbs, that is, the flow->head is null. > The root cause, as the [2] says, is because that bpf_prog_test_run_skb() > run a bpf prog which redirects empty skbs. > So we should determine whether the length of the packet modified by bpf > prog or others like bpf_prog_test is valid before forwarding it directly. > > LINK: [1] https://syzkaller.appspot.com/bug?id=0b84da80c2917757915afa89f7738a9d16ec96c5 > LINK: [2] https://www.spinics.net/lists/netdev/msg777503.html > > Reported-by: syzbot+7a12909485b94426aceb@syzkaller.appspotmail.com > Signed-off-by: Zhengchao Shao > --- > v3: modify debug print > v2: need move checking to convert___skb_to_skb and add debug info > v1: should not check len in fast path > > include/linux/skbuff.h | 8 ++++++++ > net/bpf/test_run.c | 3 +++ > net/core/dev.c | 1 + > 3 files changed, 12 insertions(+) > > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h > index f6a27ab19202..82e8368ba6e6 100644 > --- a/include/linux/skbuff.h > +++ b/include/linux/skbuff.h > @@ -2459,6 +2459,14 @@ static inline void skb_set_tail_pointer(struct sk_buff *skb, const int offset) > > #endif /* NET_SKBUFF_DATA_USES_OFFSET */ > > +static inline void skb_assert_len(struct sk_buff *skb) > +{ > +#ifdef CONFIG_DEBUG_NET > + if (WARN_ONCE(!skb->len, "%s\n", __func__)) > + DO_ONCE_LITE(skb_dump, KERN_ERR, skb, false); > +#endif /* CONFIG_DEBUG_NET */ > +} > + > /* > * Add data to an sk_buff > */ > diff --git a/net/bpf/test_run.c b/net/bpf/test_run.c > index 2ca96acbc50a..dc9dc0bedca0 100644 > --- a/net/bpf/test_run.c > +++ b/net/bpf/test_run.c > @@ -955,6 +955,9 @@ static int convert___skb_to_skb(struct sk_buff *skb, struct __sk_buff *__skb) > { > struct qdisc_skb_cb *cb = (struct qdisc_skb_cb *)skb->cb; > > + if (!skb->len) > + return -EINVAL; From another recent report [0], I don't think this change is fixing the report from syzbot. It probably makes sense to revert this patch. afaict, This '!skb->len' test is done after if (is_l2) __skb_push(skb, hh_len); Hence, skb->len is not zero in convert___skb_to_skb(). The proper place to test skb->len is before __skb_push() to ensure there is some network header after the mac or may as well ensure "data_size_in > ETH_HLEN" at the beginning. The fix in [0] is applied. If it turns out there are other cases caused by the skb generated by test_run that needs extra fixes in bpf_redirect_*, it needs to revisit an earlier !skb->len check mentioned above and the existing test cases outside of test_progs would have to adjust accordingly. [0]: https://lore.kernel.org/bpf/20221027225537.353077-1-sdf@google.com/ > + > if (!__skb) > return 0; > > diff --git a/net/core/dev.c b/net/core/dev.c > index d588fd0a54ce..716df64fcfa5 100644 > --- a/net/core/dev.c > +++ b/net/core/dev.c > @@ -4168,6 +4168,7 @@ int __dev_queue_xmit(struct sk_buff *skb, struct net_device *sb_dev) > bool again = false; > > skb_reset_mac_header(skb); > + skb_assert_len(skb); > > if (unlikely(skb_shinfo(skb)->tx_flags & SKBTX_SCHED_TSTAMP)) > __skb_tstamp_tx(skb, NULL, NULL, skb->sk, SCM_TSTAMP_SCHED);