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 avoid use-after-free for cached IPU bio
Date: Tue, 11 Apr 2023 17:00:19 +0000 [thread overview]
Message-ID: <168123241976.4928.5772798816044756759.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230410021402.1833220-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:14:02 +0800 you wrote:
> xfstest generic/019 reports a bug:
>
> kernel BUG at mm/filemap.c:1619!
> RIP: 0010:folio_end_writeback+0x8a/0x90
> Call Trace:
> end_page_writeback+0x1c/0x60
> f2fs_write_end_io+0x199/0x420
> bio_endio+0x104/0x180
> submit_bio_noacct+0xa5/0x510
> submit_bio+0x48/0x80
> f2fs_submit_write_bio+0x35/0x300
> f2fs_submit_merged_ipu_write+0x2a0/0x2b0
> f2fs_write_single_data_page+0x838/0x8b0
> f2fs_write_cache_pages+0x379/0xa30
> f2fs_write_data_pages+0x30c/0x340
> do_writepages+0xd8/0x1b0
> __writeback_single_inode+0x44/0x370
> writeback_sb_inodes+0x233/0x4d0
> __writeback_inodes_wb+0x56/0xf0
> wb_writeback+0x1dd/0x2d0
> wb_workfn+0x367/0x4a0
> process_one_work+0x21d/0x430
> worker_thread+0x4e/0x3c0
> kthread+0x103/0x130
> ret_from_fork+0x2c/0x50
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to avoid use-after-free for cached IPU bio
https://git.kernel.org/jaegeuk/f2fs/c/5cdb422c8391
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:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 2:14 [PATCH] f2fs: fix to avoid use-after-free for cached IPU bio 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=168123241976.4928.5772798816044756759.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