From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 220273] syslog(2): conflict between "The symbolic names [...] are not exported to user space" and "Definition of SYSLOG_* constants"?
Date: Mon, 18 Aug 2025 06:44:10 +0000 [thread overview]
Message-ID: <bug-220273-11311-JAHru6dHix@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220273-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220273
--- Comment #1 from Alejandro Colomar (alx@kernel.org) ---
Hi Nathaniel,
On Thu, Jun 26, 2025 at 02:54:59PM +0000, bugzilla-daemon@kernel.org wrote:
> Over at syslog(2) we see both
>
> ```
> #include <sys/klog.h> /* Definition of SYSLOG_* constants */
> ```
>
> and
>
> ```
> The symbolic names
> are defined in the kernel source, but are not exported to user
> space; you will either need to use the numbers, or define the
> names yourself.
> ```
>
> Is there a conflict between these two? After reading the first one I spent a
> while trying to figure out why I wasn't able to use the constants in my code
> despite having the include; only much later did I notice the second one.
>
> If there's no conflict between the two, what might I be misunderstanding
> about
> the first one?
The first one is a mistake introduced by me. Sorry! I've fixed it with
this commit:
commit 3d3ffae8774c89d9e0b099dba18441c459fec2c2
Author: Alejandro Colomar <alx@kernel.org>
Date: Mon Aug 18 08:39:51 2025 +0200
man/man2/syslog.2: SYNOPSIS: Remove incorrect include
It doesn't provide any macros, as said later in the page. The
programmer must either define the macros itself, or use the raw
values.
Fixes: e5a173829179 (2021-06-20; "syslog.2: Use syscall(SYS_...);
for raw system calls")
Closes: <https://bugzilla.kernel.org/show_bug.cgi?id=220273>
Reported-by: Nathaniel Manista <nathaniel@google.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
diff --git a/man/man2/syslog.2 b/man/man2/syslog.2
index ad15f4942..1b3ba8926 100644
--- a/man/man2/syslog.2
+++ b/man/man2/syslog.2
@@ -12,7 +12,6 @@ .SH LIBRARY
.RI ( libc ,\~ \-lc )
.SH SYNOPSIS
.nf
-.BR "#include <sys/klog.h>" " /* Definition of " SYSLOG_* "
constants */"
.BR "#include <sys/syscall.h>" " /* Definition of " SYS_* "
constants */"
.B #include <unistd.h>
.P
Thanks for the report!
Have a lovely day!
Alex
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2025-08-18 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 14:54 [Bug 220273] New: syslog(2): conflict between "The symbolic names [...] are not exported to user space" and "Definition of SYSLOG_* constants"? bugzilla-daemon
2025-08-18 6:44 ` bugzilla-daemon [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=bug-220273-11311-JAHru6dHix@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.