Debian Bug report logs - #350236
/usr/share/man/man2/kill.2.gz: effect of kill send by process to itself not fully clear

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Britton Leo Kerin <bkerin_rb@letterboxes.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: /usr/share/man/man2/kill.2.gz: effect of kill send by process to itself not fully clear

Date: Fri, 27 Jan 2006 20:51:27 -0900

Package: manpages-dev
Version: 2.17-1
Severity: normal
File: /usr/share/man/man2/kill.2.gz


The nots section of the kill man page contains this paragraph:

    POSIX 1003.1-2003 requires that if a process sends a signal to
    itself, and that process does not have the signal blocked, and no
    other thread has it unblocked or is waiting for it in sigwait(),
    at least one unblocked signal must be delivered to the sending
    thread before the call of kill() returns.

Presumably this means that if a thread which doesn't have the signal
blocked in its mask raises the signal, it is gauranteed to get it
before kill returns even if all other threads do have it blocked, but
it would be nice if this were stated explicitly.  Probably language
elsewhere in the standard makes this clear, but this excert taken in
isolation leaves some room for doubt, especially given the history of
thread implementation on linux.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages manpages-dev depends on:
ii  manpages                      2.17-1     Manual pages about using a GNU/Lin

manpages-dev recommends no packages.

-- no debconf information

Message #10 received at 350236@bugs.debian.org (full text, mbox, reply):

From: "Michael Kerrisk" <mtk-manpages@gmx.net>

To: Britton Leo Kerin <bkerin_rb@letterboxes.org>,350236@bugs.debian.org

Subject: Re: Bug#350236: /usr/share/man/man2/kill.2.gz: effect of kill send by process to itself not fully clear

Date: Fri, 3 Feb 2006 04:47:18 +0100 (MET)

> The nots section of the kill man page contains this paragraph:
> 
>     POSIX 1003.1-2003 requires that if a process sends a signal to
>     itself, and that process does not have the signal blocked, and no
>     other thread has it unblocked or is waiting for it in sigwait(),
>     at least one unblocked signal must be delivered to the sending
>     thread before the call of kill() returns.
> 
> Presumably this means that if a thread which doesn't have the signal
> blocked in its mask raises the signal, it is gauranteed to get it
> before kill returns even if all other threads do have it blocked, 

Correct.

> but
> it would be nice if this were stated explicitly.  

Can you be more precise please.  What text would you like 
to see?

I have made one small change:

     and that process does not have the signal blocked

becomes

    and the sending thread does not have the signal blocked

Does this address your concern?

Cheers,

Michael

-- 
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 

Want to help with man page maintenance?  
Grab the latest tarball at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/, 
read the HOWTOHELP file and grep the source 
files for 'FIXME'.

Message #15 received at 350236-done@bugs.debian.org (full text, mbox, reply):

From: Martin Schulze <joey@infodrom.org>

To: 350236-done@bugs.debian.org

Subject: fixed

Date: Sun, 2 Apr 2006 16:59:46 +0200

Due to no further complaints I believe that this bug has been fixed with the
upload of manpages 2.22.

Regards,

	Joey

-- 
Testing? What's that? If it compiles, it is good, if it boots up, it is perfect.

Please always Cc to me when replying to me on the lists.

Send a report that this bug log contains spam.