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 9FB1C30C360; Tue, 16 Jun 2026 15:28:17 +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=1781623698; cv=none; b=rKwGyCHmqyIVEnMAeSb/22/0cUx93T0MrR5Ycv3WOOIwAe8U+VxNn+LEsGY+H1IRwTSdd1z66AhgW205YWDQUqmwKJYPb5AqjmtfhyoEG7l6J+/FGAAh1Ph78ijh4i2Qmhs7uQ+UR6YLlQoBZW2j1uRZwMY+jiZbJDK1hvwtMAw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1781623698; c=relaxed/simple; bh=dG3aCjWHzXlK/CrBaTp9hhKIOKwceiZ58uznZuOOItE=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=N4rBSBxl6nDScU4F9Fo6n3GZ7cabd/pNlfmu6mACkUUgfIFgQeSp7U4a7UOjoC8+wGX1fFOXOxurLlfoVY5cicHzepzFFAQ6vp7YPvA3VXb1kQ2Yrf8b996kne4nsmyXhEpxLJyv4NyZz2o1kaNNQmIXOKgcWOrtcq/xDuWkkMg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=RtROIlVW; 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="RtROIlVW" Received: by smtp.kernel.org (Postfix) with ESMTPSA id F0C321F000E9; Tue, 16 Jun 2026 15:28:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1781623697; bh=2YmFjgIegVntrewsDF0Sira48rsDIiamJN0j6A/1Dv4=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=RtROIlVWp62Pm1yEM72MqVFDp4zN+V66skf322uzQRJUTzdcU2/v5F6pC5CrtLGMz GGpz+G0yGi8DmBz+dDw/H5xOX0Zyh6M79p/3LxiHW4jpuuIsZmOv8C+tNKqKy8hISa zvO81AFlAjwAWiAyTgvgarnu7DV0oUKuGvTFCkS3NCKkCGYnQmfJVIdGxGRxENzJSr h/Hyl9b0M0gUA56BvWVsEs+wI51qSiNI91BLNCDUL6ePDtQiRMQLJsvzS4G0Zf0zEA NEfdIMaOJUlXooAzsqWS2R7gyJONgFRxUKM8rRg9dFTASbh2iZ+Ah0R+eFumhQye2F N7gGMV/0UhhzQ== Date: Tue, 16 Jun 2026 08:28:16 -0700 From: Jakub Kicinski To: Sabrina Dubroca Cc: syzbot , davem@davemloft.net, edumazet@google.com, horms@kernel.org, john.fastabend@gmail.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, pabeni@redhat.com, syzkaller-bugs@googlegroups.com Subject: Re: [syzbot] [net?] WARNING in tls_err_abort Message-ID: <20260616082816.4dd0f035@kernel.org> In-Reply-To: References: <6a315d48.b0403584.28d0ff.0002.GAE@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Tue, 16 Jun 2026 17:19:22 +0200 Sabrina Dubroca wrote: > I suspect err==0, and sock_error() consumed sk_err in between (the > alternative would be err > 0). > > Something like this? Makes sense, but what's eating sk_err? Don't we depend on it being set to avoid further state transitions once we hit a crypto error? I thought that's why we don't consume sk_err in recvmsg and sendmsg in the first place (we are not calling sock_error() anywhere)