From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] pppd: Provide error() implementation in pppoe-discovery
Date: Sat, 15 Oct 2016 22:33:15 +0200 [thread overview]
Message-ID: <20161015223315.47f04e55@free-electrons.com> (raw)
In-Reply-To: <1476555914-22201-1-git-send-email-Stefan.Nickl@gmail.com>
Hello,
On Sat, 15 Oct 2016 20:25:14 +0200, stefan.nickl at gmail.com wrote:
> From: Stefan Nickl <Stefan.Nickl@gmail.com>
>
> The pppoe-discovery program calls error() from the CHECK_ROOM macro
> defined in pppoe.h. Since pppoe-discovery is a standalone program not
> linked with the rest of pppd, the only way this could build is by
> linking to glibc's proprietary error(3) function instead of the function
> of the same name (but with different arguments) defined in pppd/utils.c.
>
> So with glibc this builds, but will probably crash when the assertion is
> triggered. As the assertion is unlikely to fail, nobody has noticed.
>
> The build however fails with musl libc or uClibc since they don't
> provide the doppelganger.
>
> Signed-off-by: Stefan Nickl <Stefan.Nickl@gmail.com>
Thanks for this patch. Could you submit this as a Buildroot patch? I.e
a patch that adds a patch to package/pppd/ ?
Also, can you detail how you produce this error (Buildroot defconfig
that exhibits the issue) ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-15 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 18:25 [Buildroot] [PATCH] pppd: Provide error() implementation in pppoe-discovery stefan.nickl at gmail.com
2016-10-15 20:33 ` Thomas Petazzoni [this message]
2016-10-16 20:57 ` Stefan Nickl
2016-10-16 21:14 ` Arnout Vandecappelle
2016-10-20 21:24 ` Stefan Nickl
2016-10-21 18:30 ` Arnout Vandecappelle
2016-10-23 18:56 ` Stefan Nickl
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=20161015223315.47f04e55@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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