From: syzbot <syzbot+4d81015bc10889fd12ea@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [PATCH] test 305230142ae0
Date: Fri, 10 Nov 2023 18:56:06 -0800 [thread overview]
Message-ID: <0000000000000ac1500609d79461@google.com> (raw)
In-Reply-To: <0000000000001959d30609bb5d94@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: [PATCH] test 305230142ae0
Author: eadavis@qq.com
#syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 305230142ae0
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 401ea09ae4b8..3bc6abbd64db 100644
--- a/fs/btrfs/disk-io.c
+++ b/fs/btrfs/disk-io.c
@@ -4931,7 +4931,8 @@ int btrfs_get_free_objectid(struct btrfs_root *root, u64 *objectid)
goto out;
}
- *objectid = root->free_objectid++;
+ while (exist_qgroup_rb(root->fs_info, root->free_objectid++));
+ *objectid = root->free_objectid;
ret = 0;
out:
mutex_unlock(&root->objectid_mutex);
diff --git a/fs/btrfs/qgroup.h b/fs/btrfs/qgroup.h
index 855a4f978761..a8da8e11734a 100644
--- a/fs/btrfs/qgroup.h
+++ b/fs/btrfs/qgroup.h
@@ -425,4 +425,11 @@ bool btrfs_check_quota_leak(struct btrfs_fs_info *fs_info);
int btrfs_record_squota_delta(struct btrfs_fs_info *fs_info,
struct btrfs_squota_delta *delta);
+static struct btrfs_qgroup *find_qgroup_rb(struct btrfs_fs_info *fs_info,
+ u64 qgroupid);
+
+bool exist_qgroup_rb(struct btrfs_fs_info *fs_info, u64 qgroupid)
+{
+ return find_qgroup_rb(fs_info, qgroupid);
+}
#endif
--
2.25.1
next prev parent reply other threads:[~2023-11-11 2:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 17:16 [syzbot] [btrfs?] WARNING in create_pending_snapshot syzbot
2023-11-10 6:26 ` [syzbot] [PATCH] test 305230142ae0 syzbot
2023-11-10 11:07 ` syzbot
2023-11-10 11:48 ` [PATCH] btrfs: fix warning in create_pending_snapshot Lizhi Xu
2023-11-10 20:36 ` Qu Wenruo
2023-11-11 0:43 ` [syzbot] [PATCH] test 305230142ae0 syzbot
2023-11-11 1:37 ` syzbot
2023-11-11 1:44 ` syzbot
2023-11-11 2:37 ` syzbot
2023-11-11 2:56 ` syzbot [this message]
2023-11-11 3:06 ` syzbot
2023-11-11 3:40 ` syzbot
2023-11-11 5:04 ` syzbot
[not found] ` <tencent_DB6BA6C1B369A367C96C83A36457D7735705@qq.com>
2023-11-11 6:20 ` [PATCH] btrfs: fix warning in create_pending_snapshot Matthew Wilcox
[not found] ` <tencent_82622979A3A74448177BF772E6D1736E4305@qq.com>
2023-11-11 20:48 ` [PATCH] test 305230142ae0 Qu Wenruo
2023-11-11 6:54 ` [PATCH] btrfs: fix warning in create_pending_snapshot Qu Wenruo
2023-11-12 3:13 ` [syzbot] [PATCH] test 305230142ae0 syzbot
2023-11-12 3:32 ` syzbot
2023-11-12 3:35 ` syzbot
[not found] ` <tencent_B9A7767566563D4D376C96BE36524B147409@qq.com>
2023-11-12 7:35 ` [PATCH V2] btrfs: fix warning in create_pending_snapshot Qu Wenruo
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=0000000000000ac1500609d79461@google.com \
--to=syzbot+4d81015bc10889fd12ea@syzkaller.appspotmail.com \
--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