From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 2A25B34DB74; Mon, 13 Jul 2026 20:34:09 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783974850; cv=none; b=S8aLaVbrmEYqSli0i/gfds+W6Jt3Zd8JNb3k+s/xBbatZJXdX/L45u7kQMSvELJXPXu4uMLsEjdbCB5Gg8P8c0xI5APqIV/cSb6eKHLhMxnPxb0cf8VE4X0TVxCSprC08PWfOCDrH9vTsDpYCGlqiwHmSA+d8Pry+bcVNmxyRSY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783974850; c=relaxed/simple; bh=oOgV4qEv9cggQjeWpFuU9KxELdOGDtVFI917rmWV0YQ=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=KHdErIrn4e59ZooiNvyeIThNUAuMHUYL14Rmf94+VYFKkFeU6Pgr+lMa+gM03YSDw++3yitns+fcWn8vkOPT5JdiDGZ+aBesmXZx2xjc2EaOOKA8cGK/paXvLX44zT6AZkGVTOWvEC8OoWl7aTVlA6YExb2Jh5qhNFhbjZdZeJs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=eymL7HLt; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="eymL7HLt" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A28811F00A3D; Mon, 13 Jul 2026 20:34:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783974849; bh=Ug4hhpkSS8x4vJqG0UAL5u06DZYYJLZF26nVUBBT7mQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=eymL7HLtHfcq0lK9a1DOz/HVHrJowOGxkPlLRCAhTQymPYEda9vyCwcpNurxMaJcJ 7wRXLOsx9ev8j1dwr0le4Isy+zsyzD43UBGdYXGdg93BBescFBjfNhAPTNDgq2fr/J xnB03JFdDtCUGGwxkfBcDDcGz/foVml9rCGf2zViIUWkjOJhX2zCbBT0mcIEaeHaKH NhjbcLKhz/Anv1GI1w3x2EFAPqjlH3PwOuKV9oYZpcfLMRS7gM0ikFDDdmES9SHlHj vOnjDv4l9BVC/gT5Cmf9OTIM7NgMPm0mpy9Yg8v5qkp7Fc+phnxQfbhkiG2OXjr7j9 ZK7YH5z3ETFkg== From: Sasha Levin To: stable@vger.kernel.org Cc: Sasha Levin , bigeasy@linutronix.de, willemb@google.com, kerneljasonxing@gmail.com, edumazet@google.com, pabeni@redhat.com, lulie@linux.alibaba.com, davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, dust.li@linux.alibaba.com, heiko.stuebner@cherry.de Subject: Re: [PATCH 6.1.y] net: Drop the lock in skb_may_tx_timestamp() Date: Mon, 13 Jul 2026 16:34:02 -0400 Message-ID: <20260713131907.agent5-0002@kernel.org> X-Mailer: git-send-email 2.53.0 In-Reply-To: <20260713024912.36991-1-lulie@linux.alibaba.com> References: <20260713024912.36991-1-lulie@linux.alibaba.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit > commit 983512f3a87fd8dc4c94dfa6b596b6e57df5aad7 upstream. > > skb_may_tx_timestamp() may acquire sock::sk_callback_lock. The lock must > not be taken in IRQ context, only softirq is okay. A few drivers receive > the timestamp via a dedicated interrupt and complete the TX timestamp > from that handler. This will lead to a deadlock if the lock is already > write-locked on the same CPU. Queued for 6.1.y, thanks. -- Thanks, Sasha