From: syzbot <syzbot+4d81015bc10889fd12ea@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] WARNING in create_pending_snapshot
Date: Fri, 10 Nov 2023 01:38:03 -0800 [thread overview]
Message-ID: <000000000000b60b4e0609c9131b@google.com> (raw)
In-Reply-To: <20231110062620.819348-1-lizhi.xu@windriver.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING: lock held when returning to user space in btrfs_ioctl_qgroup_create
BTRFS info (device loop0): clearing compat-ro feature flag for FREE_SPACE_TREE (0x1)
BTRFS info (device loop0): clearing compat-ro feature flag for FREE_SPACE_TREE_VALID (0x2)
BTRFS info (device loop0): checking UUID tree
================================================
WARNING: lock held when returning to user space!
6.6.0-syzkaller-15365-g305230142ae0-dirty #0 Not tainted
------------------------------------------------
syz-executor.0/5537 is leaving the kernel with locks still held!
3 locks held by syz-executor.0/5537:
#0: ffff88806e8a2608 (sb_internal#2){.+.+}-{0:0}, at: btrfs_ioctl_qgroup_create+0x103/0x200 fs/btrfs/ioctl.c:3802
#1: ffff888052082390 (btrfs_trans_num_writers){++++}-{0:0}, at: join_transaction+0x401/0xce0 fs/btrfs/transaction.c:294
#2: ffff8880520823b8 (btrfs_trans_num_extwriters){++++}-{0:0}, at: join_transaction+0x401/0xce0 fs/btrfs/transaction.c:294
Tested on:
commit: 30523014 Merge tag 'pm-6.7-rc1-2' of git://git.kernel...
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=17cb5797680000
kernel config: https://syzkaller.appspot.com/x/.config?x=beb32a598fd79db9
dashboard link: https://syzkaller.appspot.com/bug?extid=4d81015bc10889fd12ea
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11c9591f680000
next parent reply other threads:[~2023-11-10 19:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231110062620.819348-1-lizhi.xu@windriver.com>
2023-11-10 9:38 ` syzbot [this message]
[not found] <tencent_E95DB2DDFA99004F9F0DE425EC0DBA921C07@qq.com>
2023-11-12 4:01 ` [syzbot] [btrfs?] WARNING in create_pending_snapshot syzbot
[not found] <tencent_0B5D9E994CCF920DF0A5CC8DA19200DDDD07@qq.com>
2023-11-12 3:44 ` syzbot
[not found] <tencent_00362097F637DA4B987401777D66AC3DDD09@qq.com>
2023-11-12 3:25 ` syzbot
[not found] <tencent_F30036224B00740776CD66FA3C47367E9609@qq.com>
2023-11-11 5:27 ` syzbot
[not found] <tencent_BB46336B9E241B574B011B9B25C6BA6BBB08@qq.com>
2023-11-11 4:29 ` syzbot
[not found] <tencent_4FE7DB06CC92DC064989ABAECD6EC7CCB706@qq.com>
2023-11-11 3:14 ` syzbot
[not found] <tencent_A2614970C3AB4447D761576DC6D73362A305@qq.com>
2023-11-11 3:02 ` syzbot
[not found] <tencent_7F898D8FA5B10DA81205DDF3DDBA1929CF07@qq.com>
2023-11-11 2:46 ` syzbot
[not found] <tencent_A840376B576326D193688362096DE3B44405@qq.com>
2023-11-11 1:55 ` syzbot
[not found] <tencent_51DB92C1C65949A12EC3AED2CC8967F44606@qq.com>
2023-11-11 1:44 ` syzbot
[not found] <tencent_1252E00673099CEECDAECC0CAA67E306C706@qq.com>
2023-11-11 1:19 ` syzbot
[not found] <20231110110726.3060048-1-lizhi.xu@windriver.com>
2023-11-10 11:25 ` syzbot
2023-11-09 17:16 syzbot
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=000000000000b60b4e0609c9131b@google.com \
--to=syzbot+4d81015bc10889fd12ea@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.