From: David Sterba <dsterba@suse.cz>
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: David Sterba <dsterba@suse.com>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>, Boris Burkov <boris@bur.io>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org,
syzbot+81670362c283f3dd889c@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: qgroup: add missing extent changeset release
Date: Tue, 27 Aug 2024 18:03:41 +0200 [thread overview]
Message-ID: <20240827160341.GZ25962@suse.cz> (raw)
In-Reply-To: <20240827151243.63493-1-pchelkin@ispras.ru>
On Tue, Aug 27, 2024 at 06:12:43PM +0300, Fedor Pchelkin wrote:
> The extent changeset may have some additional memory dynamically allocated
> for ulist in result of clear_record_extent_bits() execution.
This can happen, as clear_record_extent_bits adds more data to the
changeset in some cases. What I don't see yet how it happens. An extent
range must be split so that a new entry is added with different bits
set. This is usual thing, but why does this happen with the quotas
disabled.
next prev parent reply other threads:[~2024-08-27 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 15:12 [PATCH] btrfs: qgroup: add missing extent changeset release Fedor Pchelkin
2024-08-27 16:03 ` David Sterba [this message]
2024-08-28 9:19 ` Fedor Pchelkin
2024-08-28 9:24 ` Qu Wenruo
2024-08-28 9:30 ` Qu Wenruo
2024-08-28 16:14 ` [PATCH v2] btrfs: qgroup: don't use extent changeset when not needed Fedor Pchelkin
2024-08-28 16:57 ` Boris Burkov
2024-08-28 21:36 ` Qu Wenruo
2024-08-28 21:56 ` David Sterba
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=20240827160341.GZ25962@suse.cz \
--to=dsterba@suse.cz \
--cc=boris@bur.io \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
--cc=stable@vger.kernel.org \
--cc=syzbot+81670362c283f3dd889c@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