From: Greg KH <gregkh@linuxfoundation.org>
To: hsimeliere.opensource@witekio.com
Cc: stable@vger.kernel.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Zhenghan Wang <wzhmmmmm@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 4.19 1/1] ida: Fix crash in ida_free when the bitmap is empty
Date: Fri, 30 Aug 2024 15:05:15 +0200 [thread overview]
Message-ID: <2024083006-childish-lumpiness-cccd@gregkh> (raw)
In-Reply-To: <20240830083010.25451-2-hsimeliere.opensource@witekio.com>
On Fri, Aug 30, 2024 at 10:29:55AM +0200, hsimeliere.opensource@witekio.com wrote:
> From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
>
> commit af73483f4e8b6f5c68c9aa63257bdd929a9c194a upstream.
>
> The IDA usually detects double-frees, but that detection failed to
> consider the case when there are no nearby IDs allocated and so we have a
> NULL bitmap rather than simply having a clear bit. Add some tests to the
> test-suite to be sure we don't inadvertently reintroduce this problem.
> Unfortunately they're quite noisy so include a message to disregard
> the warnings.
>
> Reported-by: Zhenghan Wang <wzhmmmmm@gmail.com>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Hugo SIMELIERE <hsimeliere.opensource@witekio.com>
> ---
> lib/idr.c | 2 +-
> lib/test_ida.c | 40 ++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 41 insertions(+), 1 deletion(-)
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-08-30 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 8:29 [PATCH 4.19 0/1] Fix CVE-2023-6915 hsimeliere.opensource
2024-08-30 8:29 ` [PATCH 4.19 1/1] ida: Fix crash in ida_free when the bitmap is empty hsimeliere.opensource
2024-08-30 13:05 ` Greg KH [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=2024083006-childish-lumpiness-cccd@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hsimeliere.opensource@witekio.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=willy@infradead.org \
--cc=wzhmmmmm@gmail.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