Bug 216545 - FEAT: RHEL 5 Provide minimal kernel enablers for Lustre client support in RHEL5
Summary: FEAT: RHEL 5 Provide minimal kernel enablers for Lustre client support in RHEL5
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Eric Sandeen
QA Contact: Brian Brock
Keywords: FutureFeature
Depends On:
Blocks: 196637
TreeView+ depends on / blocked
Reported: 2006-11-21 00:11 UTC by Daniel Riek
Modified: 2007-11-30 22:07 UTC (History)
5 users (show)

Clone Of:
Last Closed: 2007-02-08 00:40:11 UTC

Attachments (Terms of Use)

Comment 1 Linda Wang 2006-11-21 13:58:53 UTC
RHEL4 patchset was posted on 11/10/06... 

Comment 2 Eric Sandeen 2006-11-21 15:15:54 UTC
All mandatory patches should already be in RHEL5.  The only things not in are
the extra exported symbols, and I'm still trying to figure out the policy on that.

Comment 3 Daniel Riek 2006-11-22 01:43:20 UTC
PM ACK for consistency for the Lustre enablement that is already in.

Moving to MODIFIED

Comment 4 Linda Wang 2006-11-28 16:51:05 UTC
Moved back to assign state 'til comment#2 is resolved.  BTW, if there is no
patch required, then please close as fixed in currentrelease.

Comment 5 Eric Sandeen 2006-11-29 22:01:18 UTC
Seems to be some consensus that we can export those symbols.  I'll send patches
for RHEL4 and for RHEL5.

Comment 7 Jay Turner 2006-12-01 20:42:36 UTC
Withholding QE ack until I see the proposed patches.

Comment 10 Jay Turner 2006-12-06 13:58:20 UTC
QE ack for the symbol export change.

Comment 11 Don Zickus 2006-12-18 02:58:02 UTC

Comment 12 Don Zickus 2006-12-18 17:44:52 UTC
ignore previous useless comment
in 2.6.18-1.2910.el5

Comment 13 RHEL Product and Program Management 2007-02-08 00:40:12 UTC
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.

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