From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
syzbot+31e4659a3fe953aec2f4@syzkaller.appspotmail.com,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to don't dirty inode for readonly filesystem
Date: Wed, 12 Jun 2024 15:55:57 +0000 [thread overview]
Message-ID: <171820775712.32393.17507695192982662246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240604075636.3126389-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 4 Jun 2024 15:56:36 +0800 you wrote:
> syzbot reports f2fs bug as below:
>
> kernel BUG at fs/f2fs/inode.c:933!
> RIP: 0010:f2fs_evict_inode+0x1576/0x1590 fs/f2fs/inode.c:933
> Call Trace:
> evict+0x2a4/0x620 fs/inode.c:664
> dispose_list fs/inode.c:697 [inline]
> evict_inodes+0x5f8/0x690 fs/inode.c:747
> generic_shutdown_super+0x9d/0x2c0 fs/super.c:675
> kill_block_super+0x44/0x90 fs/super.c:1667
> kill_f2fs_super+0x303/0x3b0 fs/f2fs/super.c:4894
> deactivate_locked_super+0xc1/0x130 fs/super.c:484
> cleanup_mnt+0x426/0x4c0 fs/namespace.c:1256
> task_work_run+0x24a/0x300 kernel/task_work.c:180
> ptrace_notify+0x2cd/0x380 kernel/signal.c:2399
> ptrace_report_syscall include/linux/ptrace.h:411 [inline]
> ptrace_report_syscall_exit include/linux/ptrace.h:473 [inline]
> syscall_exit_work kernel/entry/common.c:251 [inline]
> syscall_exit_to_user_mode_prepare kernel/entry/common.c:278 [inline]
> __syscall_exit_to_user_mode_work kernel/entry/common.c:283 [inline]
> syscall_exit_to_user_mode+0x15c/0x280 kernel/entry/common.c:296
> do_syscall_64+0x50/0x110 arch/x86/entry/common.c:88
> entry_SYSCALL_64_after_hwframe+0x63/0x6b
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to don't dirty inode for readonly filesystem
https://git.kernel.org/jaegeuk/f2fs/c/192b8fb8d1c8
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:[~2024-06-12 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 7:56 [f2fs-dev] [PATCH] f2fs: fix to don't dirty inode for readonly filesystem Chao Yu
2024-06-12 15:55 ` 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=171820775712.32393.17507695192982662246.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 \
--cc=stable@vger.kernel.org \
--cc=syzbot+31e4659a3fe953aec2f4@syzkaller.appspotmail.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).