From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+d015b6c2fbb5c383bf08@syzkaller.appspotmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: don't reset unchangable mount option in f2fs_remount()
Date: Tue, 30 May 2023 23:40:24 +0000 [thread overview]
Message-ID: <168549002402.8773.6116896933670248806.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230523035822.578123-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 23 May 2023 11:58:22 +0800 you wrote:
> syzbot reports a bug as below:
>
> general protection fault, probably for non-canonical address 0xdffffc0000000009: 0000 [#1] PREEMPT SMP KASAN
> RIP: 0010:__lock_acquire+0x69/0x2000 kernel/locking/lockdep.c:4942
> Call Trace:
> lock_acquire+0x1e3/0x520 kernel/locking/lockdep.c:5691
> __raw_write_lock include/linux/rwlock_api_smp.h:209 [inline]
> _raw_write_lock+0x2e/0x40 kernel/locking/spinlock.c:300
> __drop_extent_tree+0x3ac/0x660 fs/f2fs/extent_cache.c:1100
> f2fs_drop_extent_tree+0x17/0x30 fs/f2fs/extent_cache.c:1116
> f2fs_insert_range+0x2d5/0x3c0 fs/f2fs/file.c:1664
> f2fs_fallocate+0x4e4/0x6d0 fs/f2fs/file.c:1838
> vfs_fallocate+0x54b/0x6b0 fs/open.c:324
> ksys_fallocate fs/open.c:347 [inline]
> __do_sys_fallocate fs/open.c:355 [inline]
> __se_sys_fallocate fs/open.c:353 [inline]
> __x64_sys_fallocate+0xbd/0x100 fs/open.c:353
> do_syscall_x64 arch/x86/entry/common.c:50 [inline]
> do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
> entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: don't reset unchangable mount option in f2fs_remount()
https://git.kernel.org/jaegeuk/f2fs/c/c12f1bf28196
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:[~2023-05-30 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 3:58 [f2fs-dev] [PATCH] f2fs: don't reset unchangable mount option in f2fs_remount() Chao Yu
2023-05-30 23:40 ` 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=168549002402.8773.6116896933670248806.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+d015b6c2fbb5c383bf08@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).