Bug 443842

Summary: [PATCH] allow ionice to proceed even in case it could not set priority
Product: [Fedora] Fedora Reporter: Lubomir Kundrak <lkundrak>
Component: util-linux-ngAssignee: Karel Zak <kzak>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-28 11:30:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Patch to allow ionice to proceed even in case it could not set priority none

Description Lubomir Kundrak 2008-04-23 16:54:20 UTC 
Description of problem:

Attached is a tiny patch that allows "tolerant" behavior, i.e. proceeding even 
if priority could not be set. This might be of use in case something (selinux,
old kernel, etc.) does not allow the requested scheduling priority to be set.

This could be to some extend done as follows:

ionice -c3 command || command

but the downside is that one could not really tell if what failed was setting
priority or command itself, which could result in duplicate command run.

This patch solves the situation, so that user can do

ionice -t -c3 command

instead.

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

Applies to util-linux-ng-2.13.1-9
Comment 1 Lubomir Kundrak 2008-04-23 16:54:20 UTC 
Created attachment 303524 [details]
Patch to allow ionice to proceed even in case it could not set priority
Comment 2 Karel Zak 2008-04-28 11:30:10 UTC 
Redirected to the upstream mailing list. Thanks.