From nobody Thu Oct 3 01:56:11 2024 X-Original-To: net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XJvsl4R9mz5YRcY for ; Thu, 03 Oct 2024 01:56:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XJvsl2MRZz41Cj for ; Thu, 3 Oct 2024 01:56:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727920571; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vXRTi8QNBayvqpfjv04H+U+fddo4s6cFnqWq/4Qt9/I=; b=KcQzHJgN0kudfvjyAFZ3xdIlmpQxFEeSEYZJbPoVypj++V8mrMrDX5n5RQUtUXelsU6Obu LC1dE/luKMWrr8MbSJqrpoucWhO5yz8miHIRZBBkTv7sC6KYmPwWS5HmD7Cifn7K72mwil Msg2NDZ47c7bV5WOHgiLGmqwyLdfSDWt/G5SzGFNW5QbsN0Ie1m2nVvvw1Yw3A260N8P+j 7Kj8pp+3dFNcst+Zhy+AMg5LpzBKGJbguiSJxNmwtIvGCkksEDR1yGQEv9HQNwqhCBlsaV LfB6RwRDlG1GzGXFycTx3thIAgsLy30Dqy20a/GGL8WNGyJuCJBZwHpoQcMVEQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727920571; a=rsa-sha256; cv=none; b=Za3a0sZXQEyXJkTVRfj9wAZigfXFisPRynehpwVGZsDfACiBEwXG6Ip/941MxV7RWYpxbl XXGe4Sl1qy8+57HHsiG71sSXM0BABP+UK5l74BeAU50rwbwwK8L9W+wfZY990EZgCK7oxk 8AIGaRbjBYdG08/iKVbjIZOln8QxCvOSKsSYxWR3w3Apc2KprBho/ncsiUy8N0lOVAluV0 25v7qVzv1Jcu2iNMz2iMJcyuOSvhhg45wWmj9JMYYK4Yf/V6WC1BoXsqAPHaXxUhJnQetb dJsQYrDZSVPywRVH1FBL7kjMGdkPjBZFYOSCDEa06Z1ReAGeBwntDqfA9gbgoA== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4XJvsl2001zWNC for ; Thu, 3 Oct 2024 01:56:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 4931uBrl080599 for ; Thu, 3 Oct 2024 01:56:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 4931uBL6080598 for net@FreeBSD.org; Thu, 3 Oct 2024 01:56:11 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 281560] gve (4) uma deadlock during high tcp throughput Date: Thu, 03 Oct 2024 01:56:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 14.1-RELEASE X-Bugzilla-Keywords: vendor X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281560 --- Comment #19 from Konstantin Belousov --- (In reply to shailend from comment #18) Locks (except spinlocks) do not have any magic properties WRT disabling scheduling. So it is absolutely fine for a thread owning a lock to be put off CPU if there is another thread with higher priority. OTOH, for locks like mutexes and rwlocks (that use turnstiles) the system propagates priorities from lock contenders to lock owners to avoid priority inversion. Which raises the question, what is the priority of that running tx thread vs the priority of the lock owner? Could it be that the tx thread was assigned too high priority, causing this live-lock? --=20 You are receiving this mail because: You are the assignee for the bug.=