From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix lock priority inversion issue
Date: Tue, 10 Feb 2026 21:28:29 +0000 [thread overview]
Message-ID: <177075890907.3671709.18125640893352806832.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260130132809.59707-1-chao@kernel.org>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
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
prev parent reply other threads:[~2026-02-10 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 13:28 Chao Yu
2026-01-30 13:28 ` [PATCH 2/2] f2fs: introduce trace_f2fs_priority_update Chao Yu
2026-01-31 2:50 ` [PATCH 1/2] f2fs: fix lock priority inversion issue Barry Song
2026-02-03 7:00 ` Chao Yu
2026-02-10 21:28 ` patchwork-bot+f2fs [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177075890907.3671709.18125640893352806832.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome