From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jianan Huang <jnhuang95@gmail.com>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: quota: fix stale lock holder on remount failure
Date: Mon, 14 Sep 2026 15:30:06 +0000 [thread overview]
Message-ID: <178939980663.647967.17495225245064367984.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260909114615.1390443-1-jnhuang95@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 9 Sep 2026 19:46:14 +0800 you wrote:
> F2FS remount can fail while duplicating a journalled quota file name.
>
> f2fs_remount()
> - sbi->umount_lock_holder = current
> - kstrdup(F2FS_OPTION(sbi).s_qf_names[i])
> : fails
> - free previously duplicated names
> - return -ENOMEM
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: quota: fix stale lock holder on remount failure
https://git.kernel.org/jaegeuk/f2fs/c/3f140a60c92a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-09-14 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 11:46 [f2fs-dev] [PATCH v2] f2fs: quota: fix stale lock holder on remount failure Jianan Huang
2026-09-09 12:07 ` Chao Yu via Linux-f2fs-devel
2026-09-14 15:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=178939980663.647967.17495225245064367984.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=jaegeuk@kernel.org \
--cc=jnhuang95@gmail.com \
--cc=patchwork-bot+f2fs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.