From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: DJ Delorie <dj@redhat.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v1] nscd: Fix double free in netgroupcache [BZ #27462]
Date: Mon, 1 Mar 2021 13:18:55 +0530 [thread overview]
Message-ID: <2a36bac7-448b-8ebc-79bc-470efe473cf9@gotplt.org> (raw)
In-Reply-To: <xnpn0n4zrd.fsf@greed.delorie.com>
On 2/26/21 2:43 AM, DJ Delorie via Libc-alpha wrote:
>
> In commit 745664bd798ec8fd50438605948eea594179fba1 a use-after-free
> was fixed, but this led to an occasional double-free. This patch
> tracks the "live" allocation better.
>
> Tested manually by a third party.
>
> Related: RHBZ 1927877
Looks fine to me. Now that we have container testing, we should add
tests for nscd, especially since nscd doesn't seem to be going anywhere.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Siddhesh
next prev parent reply other threads:[~2021-03-01 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-25 21:13 DJ Delorie
2021-03-01 7:48 ` Siddhesh Poyarekar [this message]
2021-03-02 17:38 ` DJ Delorie
2021-03-02 17:03 ` Carlos O'Donell
2021-03-03 12:19 ` Andreas Schwab
2021-03-03 17:11 ` DJ Delorie
2021-03-03 17:48 ` Andreas Schwab
2021-03-03 19:55 ` [PATCH v1] NEWS: Add entry for CVE-2021-27645 DJ Delorie
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=2a36bac7-448b-8ebc-79bc-470efe473cf9@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).