Bug 670385 - trivial: inode number is unsigned value
Summary: trivial: inode number is unsigned value
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.6
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-18 05:45 UTC by Tetsuo Handa
Modified: 2014-06-16 22:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:04:35 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tetsuo Handa 2011-01-18 05:45:31 UTC 
Description of problem:

I noticed that SELinux's avc message prints inode number as signed value.
I think RHEL5.6's 2.6.18-238.el5 kernel wants
commit 13bddc2e9d591e31bf20020dc19ea6ca85de420e "SELinux: Use %lu for inode->i_no when printing avc".
(I don't know whether this bug breaks some application or not.)
Comment 1 RHEL Program Management 2014-03-07 12:41:23 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 2 RHEL Program Management 2014-06-02 13:04:35 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Comment 3 Tetsuo Handa 2014-06-16 22:11:26 UTC 
Response to needinfo request:
Format specifier "%lu" should be used rather than "%ld" when printing inode
number. This entry was reported more than 3 years ago but seems that nobody
else is affected. Please spend your resource to other bugs. Thank you.
Note You need to log in before you can comment on or make changes to this bug.