Skip to contentSkip to conversation

New: Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7)

Bug 14449 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 6 messages Oct 21, 2009 – Feb 8, 2010 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

http://bugzilla.kernel.org/show_bug.cgi?id=14449

               URL: http://www.nabble.com/New-test-%3A-sniperkill---killin
                    g-processes-from-a-distance-td25986571.html
           Summary: Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7)
           Product: Documentation
           Version: unspecified
    Kernel Version: Linux orangebox 2.6.30-gentoo-r4 #1 SMP PREEMPT Sat
                    Aug 8 19:31:26 PDT 2009 x86_64 Intel(R) Core(TM)2 Quad
                    CPU Q9400 @ 2.66GHz GenuineIntel GNU/Linux
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: man-pages
        AssignedTo: documentation_man-pages-ztI5WcYan/[email protected]
        ReportedBy: yaneurabeya-/[email protected]
        Regression: No

Created an attachment (id=23482)
--> (http://bugzilla.kernel.org/attachment.cgi?id=23482)
Application driven by the sniperkill script.

signal(7) states that signal # 31 for ppc, *86, etc should result in termination only, in the 3rd column, but the `will be SIGSYS' comment is unnecessarily ambiguous:

SIGUNUSED -,31,- Term Unused signal (will be SIGSYS)

SIGSYS 12,-,12 Core Bad argument to routine (SVID)

The behavior as shown in my log for the `sniperkill' test I've recommended adding to LTP demonstrates that the behavior for SIGUNUSED matches SIGSYS.

The documentation for SIGUNUSED should either clearly state a) that the process will `Core'-dump, and/or the indirection should be changed such that SIGUNUSED directly maps to SIGSYS.

I've attached the logs and test. The email to ltp-list is in the URL field.

Signature · 7 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw

[Bug 14449] Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7)

In reply to a message not in the archive

http://bugzilla.kernel.org/show_bug.cgi?id=14449

--- Comment #1 from Garrett Cooper <yaneurabeya-/[email protected]> 2009-10-21 05:35:07 --- Created an attachment (id=23483)
--> (http://bugzilla.kernel.org/attachment.cgi?id=23483)
Execution log for kernel specified.

Signature · 7 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw

[Bug 14449] Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7)

In reply to a message not in the archive

http://bugzilla.kernel.org/show_bug.cgi?id=14449

--- Comment #2 from Garrett Cooper <yaneurabeya-/[email protected]> 2009-10-21 05:35:34 --- Created an attachment (id=23484)
--> (http://bugzilla.kernel.org/attachment.cgi?id=23484)
Driver script for killme application

Signature · 7 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#4 lore raw

[Bug 14449] Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7)

In reply to a message not in the archive

http://bugzilla.kernel.org/show_bug.cgi?id=14449

Alan <alan-qBU/[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |alan-qBU/[email protected]
     Kernel Version|Linux orangebox             |2.6.30-gentoo-r4
                   |2.6.30-gentoo-r4 #1 SMP     |
                   |PREEMPT Sat Aug 8 19:31:26  |
                   |PDT 2009 x86_64 Intel(R)    |
                   |Core(TM)2 Quad CPU Q9400 @  |
                   |2.66GHz GenuineIntel        |
                   |GNU/Linux                   |
Signature · 7 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#5 lore raw

[Bug 14449] Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7)

In reply to a message not in the archive

http://bugzilla.kernel.org/show_bug.cgi?id=14449

Michael Kerrisk <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #3 from Michael Kerrisk <[email protected]> 2010-02-03 05:55:18 --- Thanks for this report. I applied the patch below. Satisfactory?

man7/signal.7 +1 -1
@@ -270,7 +270,7 @@ SIGBUS      10,7,10 Core    Bus error (bad memory access)
 SIGPOLL                Term    Pollable event (Sys V).
                        Synonym for \fBSIGIO\fP
 SIGPROF        27,27,29        Term    Profiling timer expired
-SIGSYS 12,\-,12        Core    Bad argument to routine (SVr4)
+SIGSYS 12,31,12        Core    Bad argument to routine (SVr4)
 SIGTRAP        5       Core    Trace/breakpoint trap
 SIGURG 16,23,21        Ign     Urgent condition on socket (4.2BSD)
 SIGVTALRM      26,26,28        Term    Virtual alarm clock (4.2BSD)
@@ -304,7 +304,7 @@ SIGPWR      29,30,19        Term    Power failure (System

V)

 SIGINFO        29,\-,\-                A synonym for \fBSIGPWR\fP
 SIGLOST        \-,\-,\-        Term    File lock lost
 SIGWINCH       28,28,20        Ign     Window resize signal (4.3BSD, Sun)
-SIGUNUSED      \-,31,\-        Term    Unused signal (will be \fBSIGSYS\fP)
+SIGUNUSED      \-,31,\-        Core    Synonymous with \fBSIGSYS\fP

.TE

(Signal 29 is
@@ -328,6 +328,13 @@ by default on those other Unix systems where it appears.
.B SIGIO
(which is not specified in POSIX.1-2001) is ignored by default on several other Unix systems.
+
+Where defined,
+.B SIGUNUSED
+is synonymous with
+.\" parisc is the only exception: SIGSYS is 12, SIGUNUSED is 31 +.B SIGSYS
+on most architectures.
.SS "Real-time Signals"
Linux supports real-time signals as originally defined in the POSIX.1b real-time extensions (and now included in POSIX.1-2001).

Signature · 7 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#6 lore raw

[Bug 14449] Ambiguity in SIGSYS <-> SIGUNUSED portion of signal(7)

In reply to a message not in the archive

http://bugzilla.kernel.org/show_bug.cgi?id=14449

--- Comment #4 from Garrett Cooper <yaneurabeya-/[email protected]> 2010-02-08 01:40:43 --- Sounds good -- thanks!

Signature · 7 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html