mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Bobby Bingham <koorogi@koorogi.info>
To: musl@lists.openwall.com
Subject: Re: [PATCH] fix strdupa evaulating expression twice
Date: Sun, 28 Aug 2016 12:04:38 -0500	[thread overview]
Message-ID: <20160828170438.dhcbk2my2gkcp7ot@gordon> (raw)
In-Reply-To: <CADtAWjAt4ULrnqJVk2NyjOTVWnPGAvU_MO0VM2QsqHVYo70umw@mail.gmail.com>

On Sun, Aug 28, 2016 at 04:53:50PM +0000, Noam Meltzer wrote:
> On Sun, Aug 28, 2016 at 6:08 PM Rich Felker <dalias@libc.org> wrote:
>
> > On Sun, Aug 28, 2016 at 10:59:26AM +0000, Noam Meltzer wrote:
> > >
> >
> > > From bf23b7b8fd39eaca6a05173eaf543e1bce3319ab Mon Sep 17 00:00:00 2001
> > > From: Noam Meltzer <tsnoam@gmail.com>
> > > Date: Sun, 28 Aug 2016 13:53:24 +0300
> > > Subject: [PATCH] fix strdupa evaulating expression twice
> > >
> > > calling strdupa with va_arg as its expression caused unexpected
> > > behaviour. now the expression is evaulated only once.
> > > ---
> > >  include/string.h | 5 ++++-
> > >  1 file changed, 4 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/include/string.h b/include/string.h
> > > index ff9badb..976faaf 100644
> > > --- a/include/string.h
> > > +++ b/include/string.h
> > > @@ -85,7 +85,10 @@ size_t strlcpy (char *, const char *, size_t);
> > >  #endif
> > >
> > >  #ifdef _GNU_SOURCE
> > > -#define      strdupa(x)      strcpy(alloca(strlen(x)+1),x)
> > > +#define      strdupa(x) (__extension__ ({ \
> > > +             const char *__xval = x; \
> > > +             strcpy(alloca(strlen(__xval)+1),__xval); \
> > > +     }))
> > >  int strverscmp (const char *, const char *);
> > >  int strcasecmp_l (const char *, const char *, locale_t);
> > >  int strncasecmp_l (const char *, const char *, size_t, locale_t);
> >
> > The intent of the form as written is to be actual C (modulo use of
> > alloca) rather than "GNU C". Aside from that, strdupa is essentially
> > always-unsafe and should probably be removed or at least made into a
> > warning...
> >
>
> I understand what you're saying and I tend to agree. However:
>  * The entire section of the code is wrapped with the _GNU_SOURCE test
> macro (so the __extension__ trick should work).
>  * IMHO, if strdupa is to kept, it should at least provide expected
> behaviour.

_GNU_SOURCE says that the program has requested glibc extensions, like
strdupa.  It does not imply anything about the compiler being used and
whether it implements GCC extensions.

That said, it looks like glibc only defines strdupa #if __GNUC__, so
this function is simply unavailable when using a compiler that doesn't
implement this extension.

I'm not sure what the musl policy is here, but maybe we could do
something similar?

>
> p.s.
> I spent about a day of work chasing a bug caused by the current
> implementation. So what I actually looking for is to save this pain from
> others one way or another.
>
>  - Noam


  reply	other threads:[~2016-08-28 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 10:59 Noam Meltzer
2016-08-28 15:08 ` Rich Felker
2016-08-28 16:53   ` Noam Meltzer
2016-08-28 17:04     ` Bobby Bingham [this message]
2016-08-29  5:40       ` Noam Meltzer
2016-08-30 21:03         ` Rich Felker

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=20160828170438.dhcbk2my2gkcp7ot@gordon \
    --to=koorogi@koorogi.info \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).