Bug 443823 - ionice.1 doesn't to reflect idle class changes in 2.6.25
Summary: ionice.1 doesn't to reflect idle class changes in 2.6.25
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: util-linux-ng
Version: 8
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karel Zak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-23 15:24 UTC by Lubomir Kundrak
Modified: 2008-04-28 10:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-28 10:46:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lubomir Kundrak 2008-04-23 15:24:44 UTC
Description of problem:

$ ionice -c3 :
ioprio_set: Operation not permitted
$ 

Version-Release number of selected component (if applicable):

These don't work:

kernel-2.6.24.4-84.fc8
kernel-2.6.18-53.1.13.el5

2.6.25 in Fedora works fine.

Additional info:

Actually this is documented in ionice(1) manual:

       Idle.   A  program running with idle io priority will only get disk time
when no other program has asked for disk io for a defined grace period. The
impact of
       idle io processes on normal system activity should be zero. This
scheduling class does not take a priority argument. This scheduling class  is 
not  permitted
       for an ordinary (i.e., non-root) user.

Adding Karel to Cc:, since he maintains package that contains this manual page,
and IIRC he's also upstream for it, so he should probably adjust the manual page
to reflect the fact that at least in 2.6.25 the situation is different.

Comment 1 Dave Jones 2008-04-24 11:29:57 UTC
Due to the merging of a variant of http://lwn.net/Articles/266256/ for 2.6.25
We'll pick this up soon when we rebase F8's kernel.



Comment 2 Chuck Ebbert 2008-04-25 13:07:07 UTC
Uh, not really a kernel bug.

Comment 3 Karel Zak 2008-04-28 10:46:26 UTC
The man page updated in F8, F9 and upstream git tree. Thanks!


Note You need to log in before you can comment on or make changes to this bug.