From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 6F18F38E5DA for ; Mon, 6 Apr 2026 18:14:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775499257; cv=none; b=Ykwbu82g3FzOcFP4hGrMEA6csjzBmfX7UjkSvJCUvxTw9g6tLumE5FTyNI+toD6WrNX9ejx3sxfo8rsfVdaueG2A/dY6IghAZWA3aTFgWmLqDVpYSQm4c0ekH659BtI/lPdX2LFXCm3ACAwjVJzOkIRPkRCJXtzlxkUE9da0Bvw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775499257; c=relaxed/simple; bh=qUdOjEAMvmH7efMDC7D2HhPL8uzmdroQVyLsnXvG5Wg=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=BpeYP9+RvtvmasknvgVz4b699G6Bq/NJzD8eTPX0lWQB0Hk4b02Ej8hSW5uE/3mvtw5XObwaHxa9K4Y8+IZTrFqFfqUiIduJ2scbeTnS7HHtm08D41x0KlAnMc8I+6KKM5vFfBaJlMcjBFQLXWMuggUZlpKLRmPWlzorh2bcjzE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=cUaeIvOI; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="cUaeIvOI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6D5B0C4CEF7; Mon, 6 Apr 2026 18:14:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775499257; bh=qUdOjEAMvmH7efMDC7D2HhPL8uzmdroQVyLsnXvG5Wg=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=cUaeIvOIJLaA5vnSQNHwTX0g8gt5UPDp+v0C43t+z4dA6LA5Rkc653SaaF3u7VSwr ZMIVn+cwFnfBmtqBO6TKgi4Hl9YbWPsJswHmfFaIDFmw5QazcDisxbQxJGHI58CiSL 3o4ISsRq7WGvsR0whTuAi79XI3xUFFZFudjzczHNac8r2Q0ZrlWyDZTFznYNlR5nvG +6TimnMd770JhbkULYHofa5xQzqZD3svYAF8UZ+CNY+USfLtOqm1uRnrUQrwHWvAGb EyPu7ax68A3WRYC+3zuPdqgw/LnrsUFBlPKlMel5oQNVcgAlHqrW/0UkyLnzdmjLwi 87IqbeebjYDAQ== Message-ID: Date: Mon, 6 Apr 2026 12:14:15 -0600 Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH net v2 1/1] net: l3mdev: Ignore non-L3 uppers in l3mdev_fib_table_rcu Content-Language: en-US To: Ido Schimmel , Ao Zhou Cc: netdev@vger.kernel.org, "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Simon Horman , Ido Schimmel , Jiri Pirko , Yifan Wu , Juefei Pu , Yuan Tan , Xin Liu , Haoze Xie References: <429dd4a81d4ca5624ab9f6d7b53c5fe08552c734.1775443332.git.royenheart@gmail.com> <20260406154808.GA714138@shredder> From: David Ahern In-Reply-To: <20260406154808.GA714138@shredder> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 4/6/26 9:48 AM, Ido Schimmel wrote: > > Don't we have the same problem in l3mdev_l3_rcv() and l3mdev_l3_out()? > If so, please check if I missed more places and include them in v3. > > And I think that the part that I was missing earlier is that we don't > have RCU synchronization in the unslaving path, so an RCU reader can > either see the original master, NULL or a new master (e.g., bridge > instead of the original VRF master). synchronize_rcu after the unlink (control path) seems like a better, more robust option than adding more checks to the datapath.