Bug 77498

Summary:	lilo 22.3.4 causes kernel (2.4.18-17.8.0) to panic when image is on lv
Product:	[Retired] Red Hat Linux	Reporter:	VVRVSBARANYI Zoltan <vbzoli>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	8.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-09-30 15:40: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:

Description VVRVSBARANYI Zoltan 2002-11-07 23:31:56 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020913

Description of problem:
The configured kernel image is on a logical volume. 
When lilo is called the kernel panics. 


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


How reproducible:
Always

Steps to Reproduce:
1. get lilo 22.3.4, compile, install
2. create a logical volume, put the kernel image on it
3. create lilo.conf, run lilo
	

Actual Results:  Kernel panicked. Easy to reproduce. The same behaviour with 
previous kernels and also on RH 7.3.

Expected Results:  Ok, lilo shouldn't cause kernel panic. If this method of
kernel placement is not supported it (the kernel) should report an error.

Additional info:

The bug is caused by the LV_BMAP ioctl call from the lilo's geometry.c. In fact
there is a notice in that source file about some widely distributed kernels
which seem to just oops during that call. Anyway, it should not happen IMHO. (I
have not found a soultion on the net. The one-year-old LVM patch which can be
found is for much older kernels.)

Comment 1 Bugzilla owner 2004-09-30 15:40:10 UTC

Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/