From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
syzbot+be4a9983e95a5e25c8d3@syzkaller.appspotmail.com
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to avoid potential deadlock in f2fs_record_stop_reason()
Date: Thu, 07 Nov 2024 20:30:53 +0000 [thread overview]
Message-ID: <173101145349.2084993.4012866127488813376.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241022083623.2641434-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 22 Oct 2024 16:36:23 +0800 you wrote:
> syzbot reports deadlock issue of f2fs as below:
>
> ======================================================
> WARNING: possible circular locking dependency detected
> 6.12.0-rc3-syzkaller-00087-gc964ced77262 #0 Not tainted
> ------------------------------------------------------
> kswapd0/79 is trying to acquire lock:
> ffff888011824088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_down_write fs/f2fs/f2fs.h:2199 [inline]
> ffff888011824088 (&sbi->sb_lock){++++}-{3:3}, at: f2fs_record_stop_reason+0x52/0x1d0 fs/f2fs/super.c:4068
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to avoid potential deadlock in f2fs_record_stop_reason()
https://git.kernel.org/jaegeuk/f2fs/c/f10a890308a7
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:[~2024-11-07 20:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241022083741epcas2p3f9ca0827f9501134124fd47979e70cbc@epcms2p1>
2024-10-22 8:36 ` [f2fs-dev] [PATCH v2] f2fs: fix to avoid potential deadlock in f2fs_record_stop_reason() Chao Yu via Linux-f2fs-devel
2024-10-23 9:45 ` Daejun Park
2024-11-07 20: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=173101145349.2084993.4012866127488813376.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=syzbot+be4a9983e95a5e25c8d3@syzkaller.appspotmail.com \
/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.