From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=185.226.149.38 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1794480796; b=Wdmu3zDBfny0ZTyPosRD/z8K+XPMMxYAtstVFoPEaEmO0El4X1N6iZyt9gH2VhSJ6RXQ QTpAN2E01gGEkUQEVVqDEOSih/YO5RpXu8WD41fGDtulVmnIElKXuw0uWkXPLyMIhdhsC EY1lYg3hrgawVqXJIxh4ODSabcFnS3i8bO8P93Y4UuS+dt8R0Z/hWeDd5FvsS8MtklZib JBxOMc4orEryMnFrxqMo/qAWr50KH6T4FN5LBv1Aqi9XHw+6jZ17bTxMOIiB5KZg9cjIY myabrNzXg/pa2KfqWq8yKfS5rFZWvBdovjOHOn7C12iaZFkTDsN7ZMLkF+jiAwyDUYA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1794480796; h=DMARC-Filter:Received:DKIM-Signature:Received:Received:Message-ID: Date:MIME-Version:User-Agent:From:Subject:To:Cc:References: Content-Language:In-Reply-To:Content-Type:Content-Transfer-Encoding; bh=YkfsgtQgDkRJaBVA+m0bj+SaLpO/MI4c2Nw9+WXxjHw=; b=jDTNPSAO0i4sXCqeXJkKEHSL7IXC8Mo9R8TEkmuVB6W9hWo6gqTWJ9pdHTc3QNg6McZS hPVSGJneNeuloHVtgCZkpPfNgZOiHnOTUxNdKOeOqJEnAVNmv8cRfjoKtkv0dUAVgPN2y F3bT7SKwTUpaVjwe30CorPe4LU4uCM5RwJZ03HgFj8k4BvrfmtKbS4aA0Y0yp5BOOWAJj frRRZGRGEfWlUTWF9Woz+QnA+wUB4sphmWBMoQ8QoXKl5ZTxNL02xBiyTcz8o2h+b5KDG rMCgT8VV0cCPBu/ReGwiYF/pqTvJ/OEHSIb2wTQkGcd3tso4NH+v9e7SnI0K4NZ4LHg== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=rbox.co; spf=pass smtp.mailfrom=rbox.co; dkim=pass header.d=rbox.co header.i=@rbox.co header.a=rsa-sha256 header.s=selector1 header.b=vA5prnCr; arc=none smtp.remote-ip=185.226.149.38 Received: from mailtransmit05.runbox.com (mailtransmit05.runbox.com [185.226.149.38]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 952A7606A31C; Thu, 12 Nov 2026 10:53:16 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org 952A7606A31C Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=rbox.co Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=rbox.co Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key, unprotected) header.d=rbox.co header.i=@rbox.co header.a=rsa-sha256 header.s=selector1 header.b=vA5prnCr Received: from mailtransmit02.runbox ([10.9.9.162] helo=aibo.runbox.com) by mailtransmit05.runbox.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from ) id 1xRSQY-004vrT-LI; Thu, 12 Nov 2026 11:53:10 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rbox.co; s=selector1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: Cc:To:Subject:From:MIME-Version:Date:Message-ID; bh=YkfsgtQgDkRJaBVA+m0bj+SaLpO/MI4c2Nw9+WXxjHw=; b=vA5prnCrpzhzImvR6dL1hZ5aRx 7AZfRRw/AHFTjjH14a9+SL6btoKJD7r3qjUU6vZluBY4yiXzj4EkPT7O3tsVzytYT9F8Q6omZRhfC rjSP+lIYyhcccVt4FQ1thHaQ3EB6KMYIe/k57NBQvE7wNuU7BcbkkS9ovsfC6acXFlZtcWsM9txun FJ2/cNs1c28l736y6d8qTxoZ2gOebmT3UyROCGjzS51oBTV7NUGLlU0rIXGpJBU9fe5CFAQJcq0nj ZkQsf115+s82VBjiu2kpUJLwMUDvyKVnUlu0npvonOx6HadHmshrDy+wIJxfA6Fzg6b31WLoCZrH5 IrE54w5A==; Received: from [10.9.9.74] (helo=submission03.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1xRSQT-0004QY-4T; Thu, 12 Nov 2026 11:53:05 +0100 Received: by submission03.runbox with esmtpsa [Authenticated ID (604044)] (TLS1.2:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.95) id 1xRSQD-005W3c-UH; Thu, 12 Nov 2026 11:52:50 +0100 Message-ID: Date: Thu, 12 Nov 2026 11:52:48 +0100 X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Michal Luczaj Subject: Re: [PATCH net] vhost/vsock: Fix socket state constant To: netdev-bot+sinfo@kernel.org Cc: Stefan Hajnoczi , Stefano Garzarella , Bobby Eshleman , "Michael S. Tsirkin" , Jason Wang , =?UTF-8?Q?Eugenio_P=C3=A9rez?= , "David S. Miller" , kvm@vger.kernel.org, virtualization@lists.linux.dev, netdev@vger.kernel.org, linux-kernel@vger.kernel.org References: <20261112-transport-reset-state-fix-v1-1-5698375f52a9@rbox.co> <179447976386.2168702.18392043659968828325@kernel.org> Content-Language: pl-PL, en-GB In-Reply-To: <179447976386.2168702.18392043659968828325@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 11/12/26 11:36, netdev-bot+sinfo@kernel.org wrote: > - How the issue was discovered, e.g. hit in production, hit during > development, syzbot report, manual code inspection, LLM or static > analysis tool scan. Discovered by reading the code and not getting it. > - Whether the issue was actually triggered, or is only theoretical > (e.g. found by LLM and not proven at runtime). If it was triggered > please include the symptoms, like the stack trace or kernel messages. Not triggered at runtime. It's a correctness fix, I didn't try to work out what could/would actually go wrong.