Your message dated Mon, 22 Oct 2012 22:05:11 +0200
with message-id <[email protected]>
and subject line Re: Bug#652443: ioprio_get(2): document who==0
has caused the Debian Bug report #652443,
regarding ioprio_get(2): document who==0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
652443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652443
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: manpages-dev
Version: 3.32-0.2
Severity: wishlist
File: /usr/share/man/man2/ioprio_get.2.gz
The ioprio_get(2) manual page describes the meanings of the which
and who parameters:
> IOPRIO_WHO_PROCESS
> who is a process ID identifying a single process.
>
> IOPRIO_WHO_PGRP
> who is a process group ID identifying all the members of
> a process group.
>
> IOPRIO_WHO_USER
> who is a user ID identifying all of the processes that
> have a matching real UID.
The manual page should mention that IOPRIO_WHO_PROCESS and
IOPRIO_WHO_PGRP also allow who==0. As implemented in
fs/ioprio.c, who==0 means the calling process or its process
group. The ioprio program in util-linux already uses the
feature. This is worth documenting separately because
e.g. tcsetpgrp does not treat pgrp==0 in that way.
For IOPRIO_WHO_USER, the situation is more complex: who==0 means
the root user in ioprio_set but the current user (I think the
real UID of the calling process) in ioprio_get. (That
inconsistency might even be a bug.)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages manpages-dev depends on:
ii manpages 3.32-0.2
manpages-dev recommends no packages.
Versions of packages manpages-dev suggests:
ii man-db [man-browser] 2.6.0.2-3
-- no debconf information
pgphNYt17fPBW.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.42-1
On Sun, Jul 29, 2012 at 08:32:49AM +0200, Michael Kerrisk (man-pages) wrote:
> On Sat, Dec 17, 2011 at 11:26 PM, Kalle Olavi Niemitalo <[email protected]> wrote:
> > The ioprio_get(2) manual page describes the meanings of the which
> > and who parameters:
> >
> >> IOPRIO_WHO_PROCESS
> >> who is a process ID identifying a single process.
> >>
> >> IOPRIO_WHO_PGRP
> >> who is a process group ID identifying all the members of
> >> a process group.
> >
> > The manual page should mention that IOPRIO_WHO_PROCESS and
> > IOPRIO_WHO_PGRP also allow who==0.
>
> Yes.
>
> > As implemented in
> > fs/ioprio.c, who==0 means the calling process or its process
> > group. The ioprio program in util-linux already uses the
> > feature. This is worth documenting separately because
> > e.g. tcsetpgrp does not treat pgrp==0 in that way.
>
> Agreed, this should be documented since various APIs interpret pgrp==0
> differently. Some (e.g., killpg(2)) are like this syscall, others are
> not.
Documented by Michael in 82fdd7c7d0, already in manpages 3.42.
> >> IOPRIO_WHO_USER
> >> who is a user ID identifying all of the processes that
> >> have a matching real UID.
> >
> > For IOPRIO_WHO_USER, the situation is more complex: who==0 means
> > the root user in ioprio_set but the current user (I think the
> > real UID of the calling process) in ioprio_get. (That
> > inconsistency might even be a bug.)
Remaning items as http://bugs.debian.org/691195
--
Simon Paillard
--- End Message ---
