Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp2337236ybc; Sun, 17 Nov 2019 19:19:13 -0800 (PST) X-Google-Smtp-Source: APXvYqzgaK+AU6w9ipx+J6jkXsXLTipTRuvDGRGh5PHdf6IftZYwSHIIaPeuRhxEMt+KtxGKBskO X-Received: by 2002:a17:906:7691:: with SMTP id o17mr23160900ejm.323.1574047153594; Sun, 17 Nov 2019 19:19:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574047153; cv=none; d=google.com; s=arc-20160816; b=CzNXhG/peyrrDD1k2lG4YSNSeGa/KOAYd5pBqGtXLZxRwhj7urwoIw8eB1+g41Nd0y GTVL4hH+I+xz7DkNCLjoWcsScnx5aKx4fKCDXOr/JQruTeDD+xcdfAB59by7qIK0wBGN EQYJf3IqTa/RAeSAnW/ted9pH/DihBrDqgf6Pd8aKL0TVf87GJJfF3zjrthlCHvMb0/8 XfTOGE1OdmsGW+ofAovCDaF23H4TPj/uecLdw301WjjVi6v4yI8u9e6jrLrG+MKSYsoC qdXsLje7ThsANEUC6GIzOrUgMfWhuUEsTBjZomUDG6zCwAxKyKaSf6lrtDy+yf0N34jw jtKw== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=EOKTjNRoiWAXuUO4mhAuneVZJM6Nnq8X3tkqg7D5kS0=; b=m1QwIUdsjzueHT3bKNxYUegJ8HbLIpdPVRt+ku918LR3BvL9JHkb6HD3N1ZEM7nl0p aF7jE8+2+e5jqxmXdeTZxQdjRD7iLCZH+oj2HkO3yW/1kFsBkYcYq7z8bu2eEfFRfCwD rQYLJ+TcdQ4dSd/Ev7zS4/VX9JQuxxcKb28IxFs8/hmTg5MPXi4FHTqRUWxeAmIsZGjX gt4ywMhgmOA5cU6bZAf8jZweQG1QRJ1Jb7rEV+Ow1EPEEEmCLr28NvsP1LBKEv6M24o3 F6p/jxZq0q08KKo6EucyLQDZCYvx2HjBYNYgQfpJB4xb76bMgVZxHTSHU/qKA0pXiEtl dPFQ== 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 b15si10964119ejv.167.2019.11.17.19.18.49; Sun, 17 Nov 2019 19:19:13 -0800 (PST) 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 S1726597AbfKRDQo (ORCPT + 99 others); Sun, 17 Nov 2019 22:16:44 -0500 Received: from szxga04-in.huawei.com ([45.249.212.190]:6691 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726201AbfKRDQn (ORCPT ); Sun, 17 Nov 2019 22:16:43 -0500 Received: from DGGEMS411-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id E712EBB0D7EC82ADD967; Mon, 18 Nov 2019 11:16:40 +0800 (CST) Received: from [127.0.0.1] (10.173.222.12) by DGGEMS411-HUB.china.huawei.com (10.3.19.211) with Microsoft SMTP Server id 14.3.439.0; Mon, 18 Nov 2019 11:16:32 +0800 Subject: Re: [PATCH] vrf: Fix possible NULL pointer oops when delete nic To: David Ahern , , , CC: , , , References: <60e827cb-2bba-2b7e-55dc-651103e9905f@huawei.com> <7fe948a8-debd-e336-9584-e66153e90701@gmail.com> From: "wangxiaogang (F)" Message-ID: Date: Mon, 18 Nov 2019 11:16:31 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <7fe948a8-debd-e336-9584-e66153e90701@gmail.com> Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.173.222.12] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/11/16 0:59, David Ahern wrote: > On 11/14/19 11:22 PM, wangxiaogang (F) wrote: >> diff --git a/drivers/net/vrf.c b/drivers/net/vrf.c >> index b8228f5..86c4b8c 100644 >> --- a/drivers/net/vrf.c >> +++ b/drivers/net/vrf.c >> @@ -1427,6 +1427,9 @@ static int vrf_device_event(struct notifier_block *unused, >> goto out; >> >> vrf_dev = netdev_master_upper_dev_get(dev); >> + if (!vrf_dev) >> + goto out; >> + >> vrf_del_slave(vrf_dev, dev); >> } >> out: > > BTW, I believe this is the wrong fix. A device can not be a VRF slave > AND not have an upper device. Something is fundamentally wrong. > > this problem occurs when our testers deleted the NIC and vrf in parallel. I will try to recurring this problem later.