From: Sam James <sam@gentoo.org>
To: Qu Wenruo <wqu@suse.com>
Cc: boris@bur.io, kernel-team@fb.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: fix racy bitfield write in btrfs_clear_space_info_full()
Date: Mon, 17 Nov 2025 10:07:25 +0000 [thread overview]
Message-ID: <87qztxx99e.fsf@gentoo.org> (raw)
In-Reply-To: <7a15f000-4a11-4ea5-ba74-a311077439cc@suse.com>
Qu Wenruo <wqu@suse.com> writes:
> 在 2025/11/17 20:18, Sam James 写道:
>> Has this one been taken into a tree yet? We've been "backporting" it for
>> a while now.
>
> It's already in our for-next tree, which will be pushed upstream in
> v6.19 release.
Ah, sorry for missing it. Thanks!
>
> Thanks,
> Qu
prev parent reply other threads:[~2025-11-17 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 18:50 [PATCH v2] btrfs: fix racy bitfield write in btrfs_clear_space_info_full() Boris Burkov
2025-10-02 22:16 ` Qu Wenruo
2025-11-17 9:48 ` Sam James
2025-11-17 9:52 ` Qu Wenruo
2025-11-17 10:07 ` Sam James [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=87qztxx99e.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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