From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 61F4333A010 for ; Tue, 10 Feb 2026 21:28:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770758914; cv=none; b=WBRcUsHvfBGs342kXvSM4NL/agoqyTne6cXakKc12+CMtxIpiJATjfnB5bOHReuOO0U3VkwBa7wOo2lBcvAgMRSliygxj1uzIp8c9QLzRoU8N0xg/B7caiN5h3M4hnp5Dujnv7djTYuo1QJhYa89mIfX6fdX/tstXInF5ZcNq/Y= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770758914; c=relaxed/simple; bh=wQHMv6Mf1rtk6NqvUFMPZ0OXiJzQwDvHAWYVzvrJtEQ=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=oAxEykrS7HkmXAAN/rOLCvfxG10+3Cwf8f1jPzRXGd6DRB6pKlmrQTmUC/brn8P+K7+D1NPBYn45XXr52TwiUkmoh6KcfbF29fyILFTHDvnCLCziVcsDdcbWQNBza8SAxq30mWHpCCr6boa7WjCqPj/sTE9t0HDct4ebj0d5vP0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=sPe1XVZm; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="sPe1XVZm" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 18C52C19424; Tue, 10 Feb 2026 21:28:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1770758914; bh=wQHMv6Mf1rtk6NqvUFMPZ0OXiJzQwDvHAWYVzvrJtEQ=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=sPe1XVZm/jmZHjxj3u9FpnNrr48+ssMLMxS8n0ZKCVrdTXFT+gpMoEkonqjWLe3xy Vb9S8xM0j/boJx6eMCY/XLoZigZgnMJ50cerkXp2rOvH5NQf0jGvdXaFz0hhqhSltq 1Jw+eW6kiDy0IlHWjOGp6LmGN652SXnqw+Sro7PtAQG+eS28kONQsmlXDFjQgo/Cfn I20bVTnE3/XA4w9yfdnlABBwdA9Ondr3iQHPjEnu351/tqz6tnDmUWsuV2ZL5UkSs6 W1a3duWkhLtAALJQSxH2Q3R4DMmtLEwW/oZ5sVpHm/viwshZSO/7vot5ohHdLgLfE0 eUembh+vNO5UQ== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 84F9739E3B79; Tue, 10 Feb 2026 21:28:30 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix lock priority inversion issue From: patchwork-bot+f2fs@kernel.org Message-Id: <177075890907.3671709.18125640893352806832.git-patchwork-notify@kernel.org> Date: Tue, 10 Feb 2026 21:28:29 +0000 References: <20260130132809.59707-1-chao@kernel.org> In-Reply-To: <20260130132809.59707-1-chao@kernel.org> To: Chao Yu Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Hello: This series was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Fri, 30 Jan 2026 21:28:08 +0800 you wrote: > If userspace thread has held f2fs rw semaphore, due to its low priority, > it could be runnable or preempted state for long time, during the time, > it will block high priority thread which is trying to grab the same rw > semaphore, e.g. cp_rwsem, io_rwsem... > > To fix such issue, let's detect thread's priority when it tries to grab > f2fs_rwsem lock, if the priority is lower than a priority threshold, let's > uplift the priority before it enters into critical region of lock, and > restore the priority after it leaves from critical region. > > [...] Here is the summary with links: - [f2fs-dev,1/2] f2fs: fix lock priority inversion issue https://git.kernel.org/jaegeuk/f2fs/c/07de55cbf576 - [f2fs-dev,2/2] f2fs: introduce trace_f2fs_priority_update https://git.kernel.org/jaegeuk/f2fs/c/bc367775f602 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html