From: patchwork-bot+f2fs@kernel.org
To: Bo Ye <bo.ye@mediatek.com>
Cc: yongdong.zhang@mediatek.com, linux-kernel@vger.kernel.org,
light.hsieh@mediatek.com, linux-f2fs-devel@lists.sourceforge.net,
qilin.tan@mediatek.com, linux-mediatek@lists.infradead.org,
browse.zhang@mediatek.com, matthias.bgg@gmail.com,
jaegeuk@kernel.org, peng.zhou@mediatek.com,
linux-arm-kernel@lists.infradead.org,
angelogioacchino.delregno@collabora.com
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix iostat lock protection
Date: Mon, 03 Apr 2023 18:30:18 +0000 [thread overview]
Message-ID: <168054661859.14597.6329451701329861497.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230331092658.72386-1-bo.ye@mediatek.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 31 Mar 2023 17:26:56 +0800 you wrote:
> From: Qilin Tan <qilin.tan@mediatek.com>
>
> Made iostat lock irq safe to avoid potentinal deadlock.
>
> Deadlock scenario:
> f2fs_attr_store
> -> f2fs_sbi_store
> -> _sbi_store
> -> spin_lock(sbi->iostat_lock)
> <interrupt request>
> -> scsi_end_request
> -> bio_endio
> -> f2fs_dio_read_end_io
> -> f2fs_update_iostat
> -> spin_lock_irqsave(sbi->iostat_lock) ===> Dead lock here
>
> [...]
Here is the summary with links:
- [f2fs-dev,1/2] f2fs: fix iostat lock protection
https://git.kernel.org/jaegeuk/f2fs/c/daa080db4e7e
- [f2fs-dev,2/2] f2fs: add __pack attribute for extent_info
(no matching commit)
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:[~2023-04-03 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 9:26 [f2fs-dev] [PATCH 1/2] f2fs: fix iostat lock protection Bo Ye via Linux-f2fs-devel
2023-03-31 9:26 ` [f2fs-dev] [PATCH 2/2] f2fs: add __pack attribute for extent_info Bo Ye via Linux-f2fs-devel
2023-04-01 1:00 ` Chao Yu
2023-04-01 0:53 ` [f2fs-dev] [PATCH 1/2] f2fs: fix iostat lock protection Chao Yu
2023-04-03 18:30 ` 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=168054661859.14597.6329451701329861497.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=bo.ye@mediatek.com \
--cc=browse.zhang@mediatek.com \
--cc=jaegeuk@kernel.org \
--cc=light.hsieh@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=peng.zhou@mediatek.com \
--cc=qilin.tan@mediatek.com \
--cc=yongdong.zhang@mediatek.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 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).