From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: DJ Delorie <dj@redhat.com>
Cc: fweimer@redhat.com, libc-alpha@sourceware.org
Subject: Re: [PATCH] malloc: Add missing arena lock in mallinfo [BZ #22408]
Date: Wed, 15 Nov 2017 03:31:00 -0000 [thread overview]
Message-ID: <e0193e75-dfb5-ff9f-fe3f-78b486258865@gotplt.org> (raw)
In-Reply-To: <xnk1ysxqi2.fsf@greed.delorie.com>
On Wednesday 15 November 2017 07:17 AM, DJ Delorie wrote:
> Siddhesh Poyarekar <siddhesh@gotplt.org> writes:
>> statistics reporting in malloc_info" since it does more than adding the
>> missing arena lock. That or split out the loop to iterate over heaps
>> into a separate patch since it is a logically distinct change from the
>> fix to BZ#22408, with a bz to track the fix. I prefer the latter approach.
>
> I don't see the benefit of splitting up the patch, as there would be no
> patch left - Florian's solution did not require any changes to the
> locks. Given no obvious change specific to the BZ, I think it's OK to
> use the existing patch to close the existing BZ as "fixed by other
> means".
I don't see how you came to that conclusion, there is a fix in there
that brings heap->size into the lock scope of ar_ptr->mutex. That is
one fix and the other fix is to then expand the heap traversal so that
all heaps are accounted for. Florian's follow-up patches have correctly
made that split.
They're two very different bugs and hence should have two different
patches to clearly indicate what changed.
Siddhesh
next prev parent reply other threads:[~2017-11-15 3:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 10:51 Florian Weimer
2017-11-14 14:30 ` [PATCH] malloc: Add missing arena lock in malloc_info " Florian Weimer
2017-11-14 14:39 ` [PATCH] malloc: Add missing arena lock in mallinfo " Siddhesh Poyarekar
2017-11-14 15:09 ` Florian Weimer
2017-11-15 1:47 ` DJ Delorie
2017-11-15 3:31 ` Siddhesh Poyarekar [this message]
2017-11-15 3:53 ` DJ Delorie
2017-11-15 4:44 ` Siddhesh Poyarekar
2017-11-15 8:31 ` Florian Weimer
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=e0193e75-dfb5-ff9f-fe3f-78b486258865@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=dj@redhat.com \
--cc=fweimer@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).