From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Filipe Manana <fdmanana@kernel.org>
Cc: cve@kernel.org, linux-kernel@vger.kernel.org,
linux-cve-announce@vger.kernel.org
Subject: Re: CVE-2024-26905: btrfs: fix data races when accessing the reserved amount of block reserves
Date: Mon, 29 Jul 2024 15:07:55 +0200 [thread overview]
Message-ID: <2024072933-conical-chevy-f9c4@gregkh> (raw)
In-Reply-To: <ZqePLSiplMVebl39@debian0.Home>
On Mon, Jul 29, 2024 at 01:46:37PM +0100, Filipe Manana wrote:
> On Wed, Apr 17, 2024 at 12:29:20PM +0200, Greg Kroah-Hartman wrote:
> > Description
> > ===========
> >
> > In the Linux kernel, the following vulnerability has been resolved:
> >
> > btrfs: fix data races when accessing the reserved amount of block reserves
> >
>
> Greg, can you clarify why is this being classified as a CVE?
The text of the changelog made it sound like a race condition that was
being fixed, except for this bit:
> > So add a helper to get the reserved amount of a block reserve while
> > holding the lock. The value may be not be up to date anymore when used by
> > need_preemptive_reclaim() and btrfs_preempt_reclaim_metadata_space(), but
> > that's ok since the worst it can do is cause more reclaim work do be done
> > sooner rather than later. Reading the field while holding the lock instead
> > of using the data_race() annotation is used in order to prevent load
> > tearing.
That paragraph explains that this really isn't a vulnerability, sorry
about that. I'll go reject this CVE id now, thanks for the review!
greg k-h
prev parent reply other threads:[~2024-07-29 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024041746-CVE-2024-26905-69f0@gregkh>
2024-07-29 12:46 ` CVE-2024-26905: btrfs: fix data races when accessing the reserved amount of block reserves Filipe Manana
2024-07-29 13:07 ` Greg Kroah-Hartman [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=2024072933-conical-chevy-f9c4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=fdmanana@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--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