From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E3F6C433EF for ; Mon, 11 Apr 2022 01:11:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238849AbiDKBNw (ORCPT ); Sun, 10 Apr 2022 21:13:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53638 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229492AbiDKBNu (ORCPT ); Sun, 10 Apr 2022 21:13:50 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3FDC63A5C0; Sun, 10 Apr 2022 18:11:38 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id CE86F60EF9; Mon, 11 Apr 2022 01:11:37 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 509F6C385A1; Mon, 11 Apr 2022 01:11:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649639497; bh=fTes6JGGokhrpUq274WThThhCqdCAPEybXDIHMyHnwc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=oOXEPH+K+bkdawVLm6QgS7WbUZe1Y4g1AcfifMPfr7IRWK9XmH3R+HHrvjDTGnJfa vWjMw5PImV/9P+0ogrDTBv1KhBmN1BoztpVw8Lj66M3gtf2BKCr25qUtuA5pukJFMt GQdq6QM/capKfXb2A+yEiE0Gx61lOiaXVkoXWvifkJI4D7HdzIyu6sG0Zl/h5IzjN4 zGi4a1QJmeaOJFC1ARXOhj88xYYWOIT/0MPlL94CtsOhauEJxqJftgi4srk+TRQ0RY MIzNoh8VRAJf+5mEqm3bHB0kGxm8tDeqkmYsW02yMTlPPSb1p/M5bgyIR/eyMXg47m kDErvtt+yDeMA== Message-ID: <636075e9-8902-6909-1a7d-8dfdc395d67d@kernel.org> Date: Sun, 10 Apr 2022 19:11:31 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH net] ipv6: fix panic when forwarding a pkt with no in6 dev Content-Language: en-US To: Nicolas Dichtel , Eric Dumazet , kongweibin Cc: David Miller , Jakub Kicinski , Willem de Bruijn , Pavel Begunkov , Vasily Averin , Martin KaFai Lau , LKML , netdev , rose.chen@huawei.com, liaichun@huawei.com, stable@vger.kernel.org References: <59150cd5-9950-2479-a992-94dcdaa5e63c@6wind.com> <20220408140342.19311-1-nicolas.dichtel@6wind.com> From: David Ahern In-Reply-To: <20220408140342.19311-1-nicolas.dichtel@6wind.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/8/22 8:03 AM, Nicolas Dichtel wrote: > kongweibin reported a kernel panic in ip6_forward() when input interface > has no in6 dev associated. > > The following tc commands were used to reproduce this panic: > tc qdisc del dev vxlan100 root > tc qdisc add dev vxlan100 root netem corrupt 5% > > CC: stable@vger.kernel.org > Fixes: ccd27f05ae7b ("ipv6: fix 'disable_policy' for fwd packets") > Reported-by: kongweibin > Signed-off-by: Nicolas Dichtel > --- > Reviewed-by: David Ahern