From: Alan Coopersmith <alan.coopersmith@oracle.com>
To: libc-coord@lists.openwall.com,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Dan Raymond <draymond@foxvalley.net>,
libc-alpha@sourceware.org, Rich Felker <dalias@libc.org>
Subject: Re: [libc-coord] syslog and LOG_KERN - Re: [PATCH] Bug 3604: fix calls to openlog() with LOG_KERN facility
Date: Wed, 31 Mar 2021 12:44:57 -0700 [thread overview]
Message-ID: <9b021a51-2d91-8fc8-c13d-0cc0315ccca9@oracle.com> (raw)
In-Reply-To: <86d18b12-c12b-9837-de7a-9dcb377ed6c4@linaro.org>
On 3/31/21 12:27 PM, Adhemerval Zanella wrote:
>
>
> On 27/03/2021 17:07, Dan Raymond wrote:
>> From 93683928886a563a4740e2b42b53752a4a7d431f Mon Sep 17 00:00:00 2001
>> From: Dan Raymond <draymond@foxvalley.net>
>> Date: Sat, 27 Mar 2021 13:51:16 -0600
>> Subject: [PATCH] Bug 3604: fix calls to openlog() with LOG_KERN facility
>>
>
> Not allowing LOG_KERN by any user process seems to be de facto behavior
> on all systems I am aware of:
>
> * FreeBSD and MUSL explicit set to previous log facility (they check
> if the priority against a mask and since on both LOG_KERN is 0 is
> set to the previous/default value).
>
> * Solaris 11.4 man page explicit says:
>
> LOG_KERN Messages generated by the kernel. These cannot be gener-
> ated by any user processes.
The Solaris implementation is similar to FreeBSD & MUSL - LOG_KERN is 0,
so appears the same to syslog() as not specifying a facility and letting
the default value be used.
--
-Alan Coopersmith- alan.coopersmith@oracle.com
Oracle Solaris Engineering - https://blogs.oracle.com/alanc
next prev parent reply other threads:[~2021-03-31 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 20:07 Dan Raymond
2021-03-31 15:19 ` Dan Raymond
2021-03-31 19:27 ` syslog and LOG_KERN - " Adhemerval Zanella
2021-03-31 19:44 ` Alan Coopersmith [this message]
2021-04-01 1:21 ` ***SPAM***Re: [libc-coord] " Dan Raymond
2021-04-01 15:21 ` Rich Felker
2021-04-06 16:47 ` [PATCH] fix calls to openlog() with LOG_KERN facility (Bug 3604) Dan Raymond
2021-04-09 17:37 ` [PATCH] Bug 3604: fix calls to openlog() with LOG_KERN facility Adhemerval Zanella
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=9b021a51-2d91-8fc8-c13d-0cc0315ccca9@oracle.com \
--to=alan.coopersmith@oracle.com \
--cc=adhemerval.zanella@linaro.org \
--cc=dalias@libc.org \
--cc=draymond@foxvalley.net \
--cc=libc-alpha@sourceware.org \
--cc=libc-coord@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.
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).