Bug 569597 - posix_fadvise() handles its arguments incorrectly in 32-bit compat mode. [rhel-5.4.z]
Summary: posix_fadvise() handles its arguments incorrectly in 32-bit compat mode. [rhe...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.6
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Pirko
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On: 559410
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-01 19:53 UTC by RHEL Program Management
Modified: 2015-05-05 01:19 UTC (History)
11 users (show)

Fixed In Version: kernel-2.6.18-164.16.1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-27 12:46:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0380 0 normal SHIPPED_LIVE Important: kernel security and bug fix update 2010-04-27 12:46:01 UTC

Description RHEL Program Management 2010-03-01 19:53:28 UTC
This bug has been copied from bug #559410 and has been proposed
to be backported to 5.4 z-stream (EUS).

Comment 3 john.haxby@oracle.com 2010-03-04 17:25:32 UTC
See bug 554735 for test cases and a proposed patch.

Comment 4 Chris Lalancette 2010-03-05 13:40:25 UTC
Please note that you'll need the followup patch for the Xen kernel as well.  That was just posted, and should be integrated into the 5.5 kernel soon.

Chris Lalancette

Comment 5 Jiri Pirko 2010-03-23 10:05:54 UTC
in 2.6.18-164.16.1.el5

Comment 9 errata-xmlrpc 2010-04-27 12:46:26 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0380.html


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