From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Bug in macro LOG_MAKEPRI in syslog.h
Date: Sun, 11 Oct 2015 22:40:23 -0400 [thread overview]
Message-ID: <20151012024023.GN8645@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAPpC8L8VKkSL9KcuDLBRnoPDF-AXohtxvhy=_MbX0K4PZ11Sfg@mail.gmail.com>
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);
Upon further investigation and discussion, it looks like making this
change is the right thing to do. For example:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729666
I kind of wonder if it would be better to do something like:
#define LOG_MAKEPRI(f, p) (((f)&-8) | (p))
in case programs expecting the old definition use the result of
LOG_FAC. On the other hand this is all cruft, and LOG_FAC is probably
wrong too (anyone have a BSD definition to compare against?) so it
might make sense to just start out with a minimal change.
Best would be to get programs to stop using these bogus and
problematic macros...
Rich
prev parent reply other threads:[~2015-10-12 2:40 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
2015-10-12 2:40 ` Rich Felker [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=20151012024023.GN8645@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).