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

version graph

Package: manpages-dev; Maintainer for manpages-dev is Martin Schulze <joey@debian.org>; Source for manpages-dev is src:manpages.

Reported by: Britton Leo Kerin <bkerin_rb@letterboxes.org>

Date: Sat, 28 Jan 2006 05:48:02 UTC

Severity: normal

Found in version manpages-dev/2.17-1

Done: Martin Schulze <joey@infodrom.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Martin Schulze <joey@debian.org>:
Bug#350236; Package manpages-dev. Full text and rfc822 format available.

Acknowledgement sent to Britton Leo Kerin <bkerin_rb@letterboxes.org>:
New Bug report received and forwarded. Copy sent to Martin Schulze <joey@debian.org>. Full text and rfc822 format available.

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

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



Information forwarded to debian-bugs-dist@lists.debian.org, Martin Schulze <joey@debian.org>:
Bug#350236; Package manpages-dev. Full text and rfc822 format available.

Acknowledgement sent to "Michael Kerrisk" <mtk-manpages@gmx.net>:
Extra info received and forwarded to list. Copy sent to Martin Schulze <joey@debian.org>. Full text and rfc822 format available.

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

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'.



Reply sent to Martin Schulze <joey@infodrom.org>:
You have taken responsibility. Full text and rfc822 format available.

Notification sent to Britton Leo Kerin <bkerin_rb@letterboxes.org>:
Bug acknowledged by developer. Full text and rfc822 format available.

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

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.



Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 18 Jun 2007 00:53:27 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sun Apr 20 11:07:57 2014; Machine Name: beach.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.