public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
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:53:00 -0000	[thread overview]
Message-ID: <xnh8twxknc.fsf@greed.delorie.com> (raw)
In-Reply-To: <e0193e75-dfb5-ff9f-fe3f-78b486258865@gotplt.org> (message from Siddhesh Poyarekar on Wed, 15 Nov 2017 09:00:59 +0530)


Siddhesh Poyarekar <siddhesh@gotplt.org> writes:
> 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.

Florian's new patches move a line of code in one, and immediately remove
it in the second, just to satisfy a BZ.  I doubt the readers of the BZ
care about anything beyond "it was fixed" 99% of the time.

> They're two very different bugs and hence should have two different
> patches to clearly indicate what changed.

I don't feel too strongly about this because the code is the same in the
end, but it seems like extra work with a weak justification.  These are
the types of requirements that may put off a first-time contributor.
Obviously this doesn't apply to Florian ;-)

  reply	other threads:[~2017-11-15  3:53 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
2017-11-15  3:53       ` DJ Delorie [this message]
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=xnh8twxknc.fsf@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@gotplt.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).