From: Chao Yu <chao@kernel.org>
To: syzbot <syzbot+dd6352699b8027673b35@syzkaller.appspotmail.com>,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Cc: Eric Biggers <ebiggers@kernel.org>
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_fiemap
Date: Wed, 28 Jun 2023 16:46:51 +0800 [thread overview]
Message-ID: <55a80df7-0725-d36c-566b-24cdf2dfd6da@kernel.org> (raw)
In-Reply-To: <000000000000ded70105fef7cd35@google.com>
On 2023/6/26 1:45, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 15e71592dbae Add linux-next specific files for 20230621
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=101c827b280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=b4e51841f618f374
> dashboard link: https://syzkaller.appspot.com/bug?extid=dd6352699b8027673b35
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/6b6464ef4887/disk-15e71592.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/81eba5775318/vmlinux-15e71592.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/bc7983587629/bzImage-15e71592.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+dd6352699b8027673b35@syzkaller.appspotmail.com
>
> loop4: detected capacity change from 0 to 40427
> F2FS-fs (loop4): Found nat_bits in checkpoint
> F2FS-fs (loop4): Mounted with checkpoint version = 48b305e5
> ======================================================
> WARNING: possible circular locking dependency detected
> 6.4.0-rc7-next-20230621-syzkaller #0 Not tainted
> ------------------------------------------------------
> syz-executor.4/7658 is trying to acquire lock:
> ffff888012869e20 (&mm->mmap_lock){++++}-{3:3}, at: __might_fault+0xb2/0x190 mm/memory.c:5716
>
> but task is already holding lock:
> ffff8880865b1a10 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:771 [inline]
> ffff8880865b1a10 (&sb->s_type->i_mutex_key#23){+.+.}-{3:3}, at: f2fs_fiemap+0x1e3/0x1670 fs/f2fs/data.c:1998
This was caused by the patch
"f2fs: fix to avoid mmap vs set_compress_option case"
(https://lore.kernel.org/linux-f2fs-devel/20230529104709.2560779-1-chao@kernel.org/)
which has been dropped.
#syz set subsystems: f2fs
#syz invalid
_______________________________________________
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-06-28 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 17:45 [f2fs-dev] [syzbot] [f2fs?] possible deadlock in f2fs_fiemap syzbot
2023-06-28 8:46 ` Chao Yu [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=55a80df7-0725-d36c-566b-24cdf2dfd6da@kernel.org \
--to=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+dd6352699b8027673b35@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).