From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f49.google.com (mail-pj1-f49.google.com [209.85.216.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DBF771E9066 for ; Thu, 14 Nov 2024 06:29:54 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.216.49 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731565796; cv=none; b=Fn8YZY8kWAukKadq6AwDb7MhUz+73hJ4D9dUeyfGcuxNXP+MuSoPrOAq5Fj/f5nB5B5iEnsvSTKBgAQ5eRGqs6vqWPKjM3ekZzPB5gjGVwdORdbYfJc1cIwfNOXUhA9PpByM5LyQSVmSEulw2XuvaxNukL3T1ecp8LuBq95pW7Q= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731565796; c=relaxed/simple; bh=3+namQukeZLx2CV7DlgaX+q4V2zRXwnmPu+JiK8qS+Q=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ChrkrJm/6gYfwuzO2b4YQ8oyj1WWj0yyJgOWDuk7y3YNndjNrTXjWZFsMLqscb3LGqOM5jFc9sl6m1YTPbNhpdW1pnnKVyDHYHeUM4pRpflfcbWt6SBZCKh3Bw2BhhutvSQIsqZHDEkgyet5wWe5/bx4TUznjybYrIBcmOk1HJ4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=fastly.com; spf=pass smtp.mailfrom=fastly.com; dkim=pass (1024-bit key) header.d=fastly.com header.i=@fastly.com header.b=l/m2ar5X; arc=none smtp.client-ip=209.85.216.49 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=fastly.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=fastly.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=fastly.com header.i=@fastly.com header.b="l/m2ar5X" Received: by mail-pj1-f49.google.com with SMTP id 98e67ed59e1d1-2e2d1858cdfso227163a91.1 for ; Wed, 13 Nov 2024 22:29:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; t=1731565794; x=1732170594; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=e1U1d47krDEIIdDqbZ0ejinn2L3sss3M6fc+t7cgpMg=; b=l/m2ar5XtOzpZfn8q/ouwrOY51Lv2ELudVY5Lm0xOC+tOEJ9DSaSd04vJdpwUWY0eD TmzC6K4w/U/vFbsa8i5XzmSyzkXC9tT6k4ELz9GejE3NJvIwO67XxapY1B9+FsHmHiUY CIljGFvDMActb9dJDHZDiD6jMDqoJNOLRvELw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1731565794; x=1732170594; h=in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=e1U1d47krDEIIdDqbZ0ejinn2L3sss3M6fc+t7cgpMg=; b=eGzSymuA+1T2OkCpYOexYOohhRMUj0jZTdh2+TGxzRW6ylgrm8MAGmUwg3IJXtnjIv Lp4ccm19HTQj+Eeuj7qZy3vTfi4WOVZmiRCOYaR/mdeTvu1E4RGxcn1Ba8MVx9+WUvPa +UOy5hWB4YwOv6KVfv1Er6NoVad/aLMYCC2TvNXnzBIAEKTboWlE2TrwJxfX0gWV/aNs gtQzUksx6jzK/imGp1xZTOF/sIHE+25dMJqS7Go+qmlU+Wn+hXxWc6UrsvKSB/6QYUfp bKAPW3D+k6jWOAIg3gCHBkCcGmyLxikPBbYoTRPWtcScDkkeCtuIerPK3Hs1rRis1WnN aovA== X-Gm-Message-State: AOJu0YzoFSzr6SGnJqisrgL5xmf6DKQWspuRjw7YYXTfEnQr9EXhQ+N5 ll5SsHetWvtmdB2veMJam8zUk/2Te9cF4mEFD5n4DClmgrXFNjMptK6Zqm0y5uA= X-Google-Smtp-Source: AGHT+IEwKpd9ZK69/Lrrv6KF9AavgRm3fpHJJ9DYUNlx4ODRs/7h6HAJLacjxS3Wq18rSX5qKX82EQ== X-Received: by 2002:a17:90b:2747:b0:2e2:cf5c:8ee3 with SMTP id 98e67ed59e1d1-2e9b17138bcmr33101700a91.10.1731565793945; Wed, 13 Nov 2024 22:29:53 -0800 (PST) Received: from LQ3V64L9R2 (c-24-6-151-244.hsd1.ca.comcast.net. [24.6.151.244]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2ea024a4b49sm635461a91.26.2024.11.13.22.29.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Nov 2024 22:29:53 -0800 (PST) Date: Wed, 13 Nov 2024 22:29:50 -0800 From: Joe Damato To: Jakub Kicinski Cc: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com, amritha.nambiar@intel.com, sridhar.samudrala@intel.com, mkarsten@uwaterloo.ca, "David S. Miller" , open list , Mina Almasry , Simon Horman Subject: Re: [net v2 0/2] Fix rcu_read_lock issues in netdev-genl Message-ID: Mail-Followup-To: Joe Damato , Jakub Kicinski , netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com, amritha.nambiar@intel.com, sridhar.samudrala@intel.com, mkarsten@uwaterloo.ca, "David S. Miller" , open list , Mina Almasry , Simon Horman References: <20241113021755.11125-1-jdamato@fastly.com> <20241113184735.28416e41@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20241113184735.28416e41@kernel.org> On Wed, Nov 13, 2024 at 06:47:35PM -0800, Jakub Kicinski wrote: > On Wed, 13 Nov 2024 02:17:50 +0000 Joe Damato wrote: > > base-commit: a58f00ed24b849d449f7134fd5d86f07090fe2f5 > > which is a net-next commit.. please rebase on net I thought I asked about this in the previous thread, but I probably wasn't clear with my question. Let me try again: Patch 1 will apply to net and is a fixes and CC's stable, and fixes a similar issue to the one Paolo reported, not the exact same path, though. Patch 2 will not apply to net, because the code it fixes is not in net yet. This fixes the splat Paolo reported. So... back to the question in the cover letter from the RFC :) I suppose the right thing to do is split the series: - Rebase patch 1 on net (it applies as is) and send it on its own - Send patch 2 on its own against net-next Or... something else ?