Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1736584ybn; Thu, 26 Sep 2019 01:11:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqz9zqPifssgo2WD7GnZDhL7E1Fpbme5hHsTKjgFEKWbD25+ap3anXuS0L1/JddwS5cleRHw X-Received: by 2002:a05:6402:1a52:: with SMTP id bf18mr2196422edb.67.1569485479500; Thu, 26 Sep 2019 01:11:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569485479; cv=none; d=google.com; s=arc-20160816; b=cQCfpY9+Yo2XVWP8CMZq0SDHCueV7jsElSjN/rkuY5BJobJclNUqN+xSYuNCddMppN ybf4dP2+TcaZrtsAYbsqGSZkGcNbFFph3OI5wfEzL9jWZgUm+V+OEq5oNvk7TeFrWjQN KGhkDIFhiQdT1Mn0xNMWBnAbVSTpSiRlAVA6uZLrUYdufesPLtfaN4SRHPeadyq9jIzZ ak4jup36i+aSSvoXp3pL4U2LLfi9GP5ZCNKD5FEyil6fP6iI5QCBo4UFJrTLYK4bfYwE /nSwas6aODNg/F+LMYFeJQzeTTQd3D3pBcO7LMiCHdqk5Damjn3ABy7Dzd8NRwudFeuu BaNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date; bh=cSAzp+H4yeQ/ZoMTotLi8TEP7jklEmHK4EQyWHLG5To=; b=F/wQMYCaH7JOKbiQHbvRI4JSUSO1b8Quc6kX3RU0Yfqj7F8csBFkI5fs0s19vOGcZt o/udODYQPKX/pLRC3+juK6auILEUiEjA/H4WvWPN7G2h57Kx0bp5Dxm6jsoJUR4E8dXB qRlrHoINqZZNeO2bMfR99V9ohmpFPuytiNwKwS6QcYlfLUhVY4tzIY/gk/0dE7236LSU WOrpwwrW3R2tV1OntyxWvphtowZQJAEUHi0d/DhcdyuuT8U4eimRi/iLe4L33b4t56G/ Y0ExLo6GRPPbZivstf3dvU8YTvjioq+yx2za2Q83+3KbPwos9CIa2YDW6hmpOLDznPHU 02lg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j14si611344ejf.53.2019.09.26.01.10.55; Thu, 26 Sep 2019 01:11:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2632743AbfIXNaO (ORCPT + 99 others); Tue, 24 Sep 2019 09:30:14 -0400 Received: from shards.monkeyblade.net ([23.128.96.9]:51550 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2504934AbfIXNaO (ORCPT ); Tue, 24 Sep 2019 09:30:14 -0400 Received: from localhost (231-157-167-83.reverse.alphalink.fr [83.167.157.231]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 97DB915248DA9; Tue, 24 Sep 2019 06:30:12 -0700 (PDT) Date: Tue, 24 Sep 2019 15:30:08 +0200 (CEST) Message-Id: <20190924.153008.1663682877890370513.davem@davemloft.net> To: Jason@zx2c4.com Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH] ipv6: do not free rt if FIB_LOOKUP_NOREF is set on suppress rule From: David Miller In-Reply-To: References: <20190924073615.31704-1-Jason@zx2c4.com> <20190924.145257.2013712373872209531.davem@davemloft.net> X-Mailer: Mew version 6.8 on Emacs 26.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Tue, 24 Sep 2019 06:30:13 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: "Jason A. Donenfeld" Date: Tue, 24 Sep 2019 14:55:04 +0200 > On Tue, Sep 24, 2019 at 2:53 PM David Miller wrote: >> Please make such test cases integratabe into the selftests area for networking >> and submit it along with this fix. > > That link is for a WireGuard test-case. When we get that upstream, > those will all live in selftests/ all the same as you'd like. For now, > it's running for every kernel on https://build.wireguard.com/ which in > turn runs for every new commit. I'm asking you to make a non-wireguard test that triggers the problem. Or would you like a situation you're interested in to break from time to time. Jason, please don't be difficult about this and write a proper test case just like I would ask anyone else fixing bugs like this to write. Thank you.