Bug 9313 – valloc() is broken in glibc-2.1.3: returns are not aligned

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 9313 - valloc() is broken in glibc-2.1.3: returns are not aligned

Summary:	valloc() is broken in glibc-2.1.3: returns are not aligned

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	glibc (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Cristian Gafton
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-02-10 12:51 EST by Stephen Tweedie
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
regression test for valloc() in glibc. (299 bytes, text/plain) 2000-02-10 12:52 EST, Stephen Tweedie	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Stephen Tweedie 2000-02-10 12:51:08 EST

valloc() is a variant of malloc() intended to return page-aligned
memory areas.  It is relied on by certain programs for mmap() alignment
or for raw IO, in which cases the kernel enforces page alignment on the
user's buffers.

RH6.1 valloc() correctly aligns its return addresses.  This is no longer
true in RH6.2 beta, and code may break because of this.  In particular,
lmdd running on raw devices is now broken in 6.2 due to this problem.

I'll attach a trivial test program demonstrating the bug.

Comment 1 Stephen Tweedie 2000-02-10 12:52:59 EST

Created attachment 110 [details]
regression test for valloc() in glibc.

Comment 2 Stephen Tweedie 2000-02-23 12:11:59 EST

Confirmed fixed in glibc-2.1.3-10.

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