From: Chao Yu <chao@kernel.org>
To: Yangtao Li <frank.li@vivo.com>, jaegeuk@kernel.org
Cc: Christoph Hellwig <hch@lst.de>,
hanqi@vivo.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages()
Date: Sun, 26 Mar 2023 21:47:42 +0800 [thread overview]
Message-ID: <67aaa031-ab25-ffe4-ea56-3f3e4c0ac3d1@kernel.org> (raw)
In-Reply-To: <20230320172218.59628-1-frank.li@vivo.com>
On 2023/3/21 1:22, Yangtao Li wrote:
> BUG_ON() will be triggered when writing files concurrently,
> because the same page is writtenback multiple times.
>
> 1597 void folio_end_writeback(struct folio *folio)
> 1598 {
> ......
> 1618 if (!__folio_end_writeback(folio))
> 1619 BUG();
> ......
> 1625 }
>
> kernel BUG at mm/filemap.c:1619!
> Call Trace:
> <TASK>
> f2fs_write_end_io+0x1a0/0x370
> blk_update_request+0x6c/0x410
> blk_mq_end_request+0x15/0x130
> blk_complete_reqs+0x3c/0x50
> __do_softirq+0xb8/0x29b
> ? sort_range+0x20/0x20
> run_ksoftirqd+0x19/0x20
> smpboot_thread_fn+0x10b/0x1d0
> kthread+0xde/0x110
> ? kthread_complete_and_exit+0x20/0x20
> ret_from_fork+0x22/0x30
> </TASK>
>
> Below is the concurrency scenario:
>
> [Process A] [Process B] [Process C]
> f2fs_write_raw_pages()
> - redirty_page_for_writepage()
> - unlock page()
> f2fs_do_write_data_page()
> - lock_page()
> - clear_page_dirty_for_io()
> - set_page_writeback() [1st writeback]
> .....
> - unlock page()
>
> generic_perform_write()
> - f2fs_write_begin()
> - wait_for_stable_page()
>
> - f2fs_write_end()
> - set_page_dirty()
>
> - lock_page()
> - f2fs_do_write_data_page()
> - set_page_writeback() [2st writeback]
>
> This problem was introduced by the previous commit 7377e853967b ("f2fs:
> compress: fix potential deadlock of compress file"). All pagelocks were
> released in f2fs_write_raw_pages(), but whether the page was
> in the writeback state was ignored in the subsequent writing process.
> Let's fix it by waiting for the page to writeback before writing.
>
> Cc: Christoph Hellwig <hch@lst.de>
> Fixes: 4c8ff7095bef ("f2fs: support data compression")
> Fixes: 7377e853967b ("f2fs: compress: fix potential deadlock of compress file")
> Signed-off-by: Qi Han <hanqi@vivo.com>
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
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-03-26 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 17:22 [f2fs-dev] [PATCH v2] f2fs: compress: fix to call f2fs_wait_on_page_writeback() in f2fs_write_raw_pages() Yangtao Li via Linux-f2fs-devel
2023-03-26 13:47 ` Chao Yu [this message]
2023-03-27 16:00 ` patchwork-bot+f2fs
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=67aaa031-ab25-ffe4-ea56-3f3e4c0ac3d1@kernel.org \
--to=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=hanqi@vivo.com \
--cc=hch@lst.de \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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).