Re: [PATCH v4 1/2] f2fs: avoid NULL checkpoint thread access in sysfs
patchwork-bot+f2fs--- via Linux-f2fs-devel <[email protected]>
| Newsgroups | gmane.linux.file-systems.f2fs,gmane.linux.kernel,gmane.linux.kernel.stable |
|---|---|
| Message-ID | <178596484463.530543.6481276544684455442.git-patchwork-notify@kernel.org> |
Hello: This series was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim <[email protected]>: On Tue, 4 Aug 2026 09:48:48 +0800 you wrote: > checkpoint_merge can be enabled even when no checkpoint merge thread is > running. A read-only mount is one case: f2fs does not start > f2fs_issue_ckpt there, but ckpt_thread_ioprio is still writable through > sysfs. > > The ckpt_thread_ioprio store path updates the saved ioprio value and, > when checkpoint_merge is enabled, calls set_task_ioprio() for the > checkpoint thread. If cprc->f2fs_issue_ckpt is NULL, that dereferences a > NULL task pointer. > > [...] Here is the summary with links: - [f2fs-dev,v4,1/2] f2fs: avoid NULL checkpoint thread access in sysfs https://git.kernel.org/jaegeuk/f2fs/c/5cb33b00c8fb - [f2fs-dev,v4,2/2] f2fs: protect critical_task_priority updates with s_umount https://git.kernel.org/jaegeuk/f2fs/c/8e4692c6c165 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html