Bug 556909

Summary:	unresolved symbol sock_recvmsg_Rsmp_4c34ff14
Product:	Red Hat Enterprise Linux 3	Reporter:	Jon Thomas <jthomas>
Component:	kernel	Assignee:	Don Howard <dhoward>
Status:	CLOSED ERRATA	QA Contact:	Martin Jenner <mjenner>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.9	CC:	cward, dhoward, dornelas, jcavallaro, jwest, mmatsuya, pep, raud, tao
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-12 09:37:50 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:
Bug Depends On:
Bug Blocks:	566740

Description Jon Thomas 2010-01-19 19:23:22 UTC

Customer module is unable to load due to

sock_recvmsg_Rsmp_4c34ff14

being replaced with 

sock_recvmsg_Rsmp_07e156b1

Looks like a kabi issue.

It appears that sock_recvmsg_Rsmp_4c34ff14 is valid up to and including 2.4.21-60. However, Kernel 2.4.21-63 contains sock_recvmsg_Rsmp_07e156b1.

Tests show that if we remove patch 9052 from the 2.4.21-63 spec and build, the kernel builds with the correct symbol.

%patch9051 -p1
#%patch9052 -p1
%patch9053 -p1
%patch9054 -p1
%patch9055 -p1
%patch9056 -p1
%patch9057 -p1
%patch9058 -p1
%patch9059 -p1
%patch9060 -p1
%patch9061 -p1
%patch9062 -p1
%patch9063 -p1

Patch9052: linux-2.4.21-unix-socket-panic.patch

Comment 1 Jon Thomas 2010-01-19 23:14:59 UTC

I forget to add that this is with hugemem kernels. The one that fails is 2.4.21-63.ELhugemem.

Comment 9 Don Howard 2010-03-15 21:00:26 UTC

A patch addressing this issue has been included in kernel-2.4.21-64.EL.

Comment 29 errata-xmlrpc 2010-11-12 09:37:50 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-0882.html