From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to drop all dirty pages during umount() if cp_error is set
Date: Tue, 11 Apr 2023 17:00:19 +0000 [thread overview]
Message-ID: <168123241980.4928.10692103692042697319.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230410021222.1826966-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 10 Apr 2023 10:12:22 +0800 you wrote:
> xfstest generic/361 reports a bug as below:
>
> f2fs_bug_on(sbi, sbi->fsync_node_num);
>
> kernel BUG at fs/f2fs/super.c:1627!
> RIP: 0010:f2fs_put_super+0x3a8/0x3b0
> Call Trace:
> generic_shutdown_super+0x8c/0x1b0
> kill_block_super+0x2b/0x60
> kill_f2fs_super+0x87/0x110
> deactivate_locked_super+0x39/0x80
> deactivate_super+0x46/0x50
> cleanup_mnt+0x109/0x170
> __cleanup_mnt+0x16/0x20
> task_work_run+0x65/0xa0
> exit_to_user_mode_prepare+0x175/0x190
> syscall_exit_to_user_mode+0x25/0x50
> do_syscall_64+0x4c/0x90
> entry_SYSCALL_64_after_hwframe+0x72/0xdc
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to drop all dirty pages during umount() if cp_error is set
https://git.kernel.org/jaegeuk/f2fs/c/c9b3649a934d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-04-11 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 2:12 [PATCH] f2fs: fix to drop all dirty pages during umount() if cp_error is set Chao Yu
2023-04-11 17:00 ` 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=168123241980.4928.10692103692042697319.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=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