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 5BE622116F4 for ; Mon, 5 Oct 2026 04:13:38 +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=1791173619; cv=none; b=M8WtW4qipK1SxJXBarUx2ZSbgIJh+vg2a2eQlJ4LH4N1+AdqC8wakNlE3bA7Bym44xkCLTKU4wj6ykjRPerzUScwYyn4hUPuInP+mGfdq110VcRRW9lo0XCH2u9lVRKYXQjcSO5gTdGsZisvoTzIqMkeFxJP63exd1t1DyG6prE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791173619; c=relaxed/simple; bh=gp7PRv3WjAiMJrp0DvXpRvTv3mwC8R3NiezXzUE7FxE=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: Content-Type:MIME-Version; b=f3ncxrBK5GjVKfj3TlQJF6zLuFSsY69efNySNuRmVtmJnvVlO/lkh+WAQL3VKS2jFwP9ospBe+XL/a6Afn7RvPHFAweh88JjhRroM7IJYL3VmmPsx9mWhYYihA81gDKY7NGg6Tpl+owAbX++Ae2bJ6BCSTxsOQhb/xvKuPTGTqQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=E5rJEsTq; 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="E5rJEsTq" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 763511F000FF; Mon, 5 Oct 2026 04:13:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1791173618; bh=Z9zRtXHe/J1k/4/9wAeq1n+PwAt+ioXmV3zyjSNrjDw=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=E5rJEsTqZBG7DmS3oP/N5xH8Oyv5CiBHwS+uYkjLWw3YMRhokU7ezcU3fcqi5Qyig 7bpfcmgaLExAX8z0DtKX6GuiNLg57+Emcs76GYqme5Pg5XdEw2sOKSja8uvm59Jhh1 c3GsIioKxXJ5xKHtq51H5hnZgJHROiPNgSL5X0Je0aCTbu3eJowalsDSs49sDEmVOE 7uO/m/Su9Pn6qRnsFNLrLq6y3BTF+eyXsUc4QSqCsxLnqbgui4kDEakSPAR7JZhPfs IaEwuR7xt/Of2IS3czbmJFik4XuxshN9nHWoQjZEUpipRDTtauha55MEMomtskEJaU 1zGlU/MdSAEYA== From: netdev-bot+sinfo@kernel.org To: Tung Nguyen Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org, edumazet@kernel.org, pabeni@redhat.com, jmaloy@redhat.com, horms@kernel.org, tipc-discussion@lists.sourceforge.net, Chengfeng Ye Subject: Re: [PATCH net] tipc: fix several race conditions caused by tipc_node_write_unlock() Date: Mon, 05 Oct 2026 04:13:37 +0000 Message-ID: <179117361701.1402591.7302351631756913976@kernel.org> In-Reply-To: <20261005041053.22695-1-tung.quang.nguyen@est.tech> References: <20261005041053.22695-1-tung.quang.nguyen@est.tech> Auto-Submitted: auto-generated Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Hi! This is an automated message. This series looks like a fix, but its commit messages seem to be missing some information: - How the issue was discovered, e.g. hit in production, hit during development, syzbot report, manual code inspection, LLM or static analysis tool scan. - Whether the issue was actually triggered, or is only theoretical (e.g. found by code inspection). If it was triggered please include the symptoms, like the stack trace or error messages. Please do not repost the series just to address the above. Instead, reply to this email with the missing information, so that reviewers can take it into account. If the series needs another revision for other reasons, please include the information in the commit messages then. The evaluation is done by an LLM so it may be wrong, if you think that is the case please reply and explain.