From: syzbot <syzbot+4d81015bc10889fd12ea@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [syzbot] [PATCH] test 305230142ae0
Date: Sat, 11 Nov 2023 19:32:38 -0800 [thread overview]
Message-ID: <0000000000008d6c4d0609ec3496@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/qgroup.c b/fs/btrfs/qgroup.c
index edb84cc03237..9be5a836c9c0 100644
--- a/fs/btrfs/qgroup.c
+++ b/fs/btrfs/qgroup.c
@@ -218,6 +218,7 @@ static struct btrfs_qgroup *add_qgroup_rb(struct btrfs_fs_info *fs_info,
p = &(*p)->rb_right;
} else {
kfree(prealloc);
+ prealloc = NULL;
return qgroup;
}
}
@@ -1697,6 +1698,7 @@ int btrfs_create_qgroup(struct btrfs_trans_handle *trans, u64 qgroupid)
struct btrfs_root *quota_root;
struct btrfs_qgroup *qgroup;
struct btrfs_qgroup *prealloc = NULL;
+ u64 objid;
int ret = 0;
if (btrfs_qgroup_mode(fs_info) == BTRFS_QGROUP_MODE_DISABLED)
@@ -1727,6 +1729,8 @@ int btrfs_create_qgroup(struct btrfs_trans_handle *trans, u64 qgroupid)
spin_lock(&fs_info->qgroup_lock);
qgroup = add_qgroup_rb(fs_info, prealloc, qgroupid);
spin_unlock(&fs_info->qgroup_lock);
+ while (!prealloc && !btrfs_get_free_objectid(fs_info->tree_root,
+ &objid) && objid <= qgroupid);
prealloc = NULL;
ret = btrfs_sysfs_add_one_qgroup(fs_info, qgroup);
--
2.25.1
next prev parent reply other threads:[~2023-11-12 3:32 UTC|newest]
Thread overview: 23+ 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
2023-11-11 3:06 ` syzbot
2023-11-11 3:40 ` syzbot
2023-11-11 5:04 ` syzbot
2023-11-11 5:06 ` [PATCH] btrfs: fix warning in create_pending_snapshot Edward Adam Davis
2023-11-11 6:20 ` Matthew Wilcox
2023-11-11 8:13 ` [PATCH] test 305230142ae0 Edward Adam Davis
2023-11-11 20:48 ` 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 [this message]
2023-11-12 3:35 ` syzbot
2023-11-12 4:48 ` [PATCH V2] btrfs: fix warning in create_pending_snapshot Edward Adam Davis
2023-11-12 7:35 ` 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=0000000000008d6c4d0609ec3496@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 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.