From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix scheduling while atomic in decompression path
Date: Sun, 26 Mar 2023 21:57:58 +0800 [thread overview]
Message-ID: <4e34660e-e3c8-fba7-e5ee-d26d4df83cab@kernel.org> (raw)
In-Reply-To: <20230323224734.2041173-1-jaegeuk@kernel.org>
On 2023/3/24 6:47, Jaegeuk Kim wrote:
> [ 16.945668][ C0] Call trace:
> [ 16.945678][ C0] dump_backtrace+0x110/0x204
> [ 16.945706][ C0] dump_stack_lvl+0x84/0xbc
> [ 16.945735][ C0] __schedule_bug+0xb8/0x1ac
> [ 16.945756][ C0] __schedule+0x724/0xbdc
> [ 16.945778][ C0] schedule+0x154/0x258
> [ 16.945793][ C0] bit_wait_io+0x48/0xa4
> [ 16.945808][ C0] out_of_line_wait_on_bit+0x114/0x198
> [ 16.945824][ C0] __sync_dirty_buffer+0x1f8/0x2e8
> [ 16.945853][ C0] __f2fs_commit_super+0x140/0x1f4
> [ 16.945881][ C0] f2fs_commit_super+0x110/0x28c
> [ 16.945898][ C0] f2fs_handle_error+0x1f4/0x2f4
> [ 16.945917][ C0] f2fs_decompress_cluster+0xc4/0x450
> [ 16.945942][ C0] f2fs_end_read_compressed_page+0xc0/0xfc
> [ 16.945959][ C0] f2fs_handle_step_decompress+0x118/0x1cc
> [ 16.945978][ C0] f2fs_read_end_io+0x168/0x2b0
> [ 16.945993][ C0] bio_endio+0x25c/0x2c8
> [ 16.946015][ C0] dm_io_dec_pending+0x3e8/0x57c
> [ 16.946052][ C0] clone_endio+0x134/0x254
> [ 16.946069][ C0] bio_endio+0x25c/0x2c8
> [ 16.946084][ C0] blk_update_request+0x1d4/0x478
> [ 16.946103][ C0] scsi_end_request+0x38/0x4cc
> [ 16.946129][ C0] scsi_io_completion+0x94/0x184
> [ 16.946147][ C0] scsi_finish_command+0xe8/0x154
> [ 16.946164][ C0] scsi_complete+0x90/0x1d8
> [ 16.946181][ C0] blk_done_softirq+0xa4/0x11c
> [ 16.946198][ C0] _stext+0x184/0x614
> [ 16.946214][ C0] __irq_exit_rcu+0x78/0x144
> [ 16.946234][ C0] handle_domain_irq+0xd4/0x154
> [ 16.946260][ C0] gic_handle_irq.33881+0x5c/0x27c
> [ 16.946281][ C0] call_on_irq_stack+0x40/0x70
> [ 16.946298][ C0] do_interrupt_handler+0x48/0xa4
> [ 16.946313][ C0] el1_interrupt+0x38/0x68
> [ 16.946346][ C0] el1h_64_irq_handler+0x20/0x30
> [ 16.946362][ C0] el1h_64_irq+0x78/0x7c
> [ 16.946377][ C0] finish_task_switch+0xc8/0x3d8
> [ 16.946394][ C0] __schedule+0x600/0xbdc
> [ 16.946408][ C0] preempt_schedule_common+0x34/0x5c
> [ 16.946423][ C0] preempt_schedule+0x44/0x48
> [ 16.946438][ C0] process_one_work+0x30c/0x550
> [ 16.946456][ C0] worker_thread+0x414/0x8bc
> [ 16.946472][ C0] kthread+0x16c/0x1e0
> [ 16.946486][ C0] ret_from_fork+0x10/0x20
>
> Fixes: bff139b49d9f ("f2fs: handle decompress only post processing in softirq")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Fixes: 95fa90c9e5a7 ("f2fs: support recording errors into superblock")
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:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 22:47 [f2fs-dev] [PATCH] f2fs: fix scheduling while atomic in decompression path Jaegeuk Kim
2023-03-26 13:57 ` 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=4e34660e-e3c8-fba7-e5ee-d26d4df83cab@kernel.org \
--to=chao@kernel.org \
--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).