From: Carlos O'Donell <carlos@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: joseph@codesourcery.com
Subject: Re: [PATCH] malloc: Fix -Wuse-after-free warning in tst-mallocalign1 [BZ #26779]
Date: Tue, 1 Feb 2022 12:08:11 -0500 [thread overview]
Message-ID: <23bf1f3d-8090-3db1-2c60-5d73fe58ee3c@redhat.com> (raw)
In-Reply-To: <9e3e8db8-ccb5-cbde-d5f6-c4ee6c75b9d9@redhat.com>
On 1/31/22 10:20, Carlos O'Donell wrote:
> On 1/31/22 03:31, Andreas Schwab wrote:
>> On Jan 31 2022, Carlos O'Donell via Libc-alpha wrote:
>>
>>> +#define ALIGNED(p) (((uintptr_t )p & MALLOC_ALIGN_MASK) == 0)
>>
>> Wrong spacing.
>
> Good catch. Thanks.
>
Fixed and pushed as obvious fix.
--
Cheers,
Carlos.
prev parent reply other threads:[~2022-02-01 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 5:21 Carlos O'Donell
2022-01-31 5:32 ` Siddhesh Poyarekar
2022-01-31 6:00 ` Carlos O'Donell
2022-01-31 8:31 ` Andreas Schwab
2022-01-31 15:20 ` Carlos O'Donell
2022-02-01 17:08 ` Carlos O'Donell [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=23bf1f3d-8090-3db1-2c60-5d73fe58ee3c@redhat.com \
--to=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@linux-m68k.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).