From: patchwork-bot+f2fs@kernel.org
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: remove i_xattr_sem to avoid deadlock and fix the original issue
Date: Thu, 15 Jun 2023 18:00:23 +0000 [thread overview]
Message-ID: <168685202301.7502.14081948087591121398.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230613233940.3643362-1-jaegeuk@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 13 Jun 2023 16:39:40 -0700 you wrote:
> This reverts commit 27161f13e3c3 "f2fs: avoid race in between read xattr & write xattr".
>
> That introduced a deadlock case:
>
> Thread #1:
>
> [122554.641906][ T92] f2fs_getxattr+0xd4/0x5fc
> -> waiting for f2fs_down_read(&F2FS_I(inode)->i_xattr_sem);
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: remove i_xattr_sem to avoid deadlock and fix the original issue
https://git.kernel.org/jaegeuk/f2fs/c/c1ac6e02b5fc
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
next prev parent reply other threads:[~2023-06-15 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 23:39 [f2fs-dev] [PATCH] f2fs: remove i_xattr_sem to avoid deadlock and fix the original issue Jaegeuk Kim
2023-06-15 18:00 ` patchwork-bot+f2fs [this message]
2023-06-25 7:26 ` Chao Yu
2023-06-25 10:27 ` Chao Yu
2023-06-26 13:11 ` Jaegeuk Kim
2023-06-27 13:37 ` Chao Yu
2023-06-28 8:07 ` Jaegeuk Kim
2023-06-28 8:08 ` [f2fs-dev] [PATCH v2] f2fs: fix deadlock in i_xattr_sem and inode page lock " Jaegeuk Kim
2023-06-28 8:36 ` Chao Yu
2023-06-28 18:33 ` Jaegeuk Kim
2023-06-30 21:59 ` Jaegeuk Kim
2023-06-30 23:36 ` Chao Yu
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=168685202301.7502.14081948087591121398.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).