From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Bug in macro LOG_MAKEPRI in syslog.h
Date: Tue, 6 Oct 2015 17:14:28 -0400 [thread overview]
Message-ID: <20151006211428.GS8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <20151006210931.GR8645@brightrain.aerifal.cx>
On Tue, Oct 06, 2015 at 05:09:31PM -0400, Rich Felker wrote:
> On Tue, Oct 06, 2015 at 09:06:49PM +0200, Pepe Aracil wrote:
> > Hi all.
> >
> >
> > Now the macro is defined as:
> > #define LOG_MAKEPRI(f, p) (((f)<<3) | (p))
> > And must be:
> > #define LOG_MAKEPRI(f, p) ((f) | (p))
> >
> > The next example posts wrong facility (LOG_LOCAL1) because LOG_LOCAL1 is
> > already rotated ( #define LOG_LOCAL1 (17<<3) ).
> >
> > syslog (LOG_MAKEPRI(LOG_LOCAL1, LOG_ERROR),
> > "Unable to make network connection to %s. Error=%m", host);
>
> LOG_MAKEPRI is not supposed to be used for this; it's not even a
> standard API. The documented way to use syslog is to pass
> LOG_LOCAL1|LOG_ERROR. See the specification at
> http://pubs.opengroup.org/onlinepubs/9699919799/functions/syslog.html
>
> I agree with your reasoning that the <<3 does not make sense, but
> glibc and other historical systems, where the nonstandard macro was
> copied from, do the same, and there does not seem to be any value in
> offering an incompatible version of a nonstandard/legacy macro like
> this. Presumably you're supposed to use LOG_FAC() first to do the >>3
> if you want to use these legacy macros, as in:
>
> LOG_MAKEPRI(LOG_FAC(LOG_LOCAL1), LOG_ERROR)
>
> Yes this is ugly..
Hmm, Alexander Monakov just pointed me to this:
https://sourceware.org/bugzilla/show_bug.cgi?id=14347
So maybe we should change it. In any case I think it's a really bad
idea to use this macro since it was "wrong" for a very long time on
glibc (and on musl). The documented correct way to achieve the same
thing is simply the | operator.
Rich
next prev parent reply other threads:[~2015-10-06 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 19:06 Pepe Aracil
2015-10-06 21:09 ` Rich Felker
2015-10-06 21:14 ` Rich Felker [this message]
2015-10-12 2:40 ` 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=20151006211428.GS8645@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).