Bug 246109 - remove unused var in alloc_ldt()
remove unused var in alloc_ldt()
Status: CLOSED DUPLICATE of bug 234580
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jerome Marchand
Martin Jenner
Depends On:
  Show dependency treegraph
Reported: 2007-06-28 11:56 EDT by Jason Baron
Modified: 2013-03-06 00:59 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-06-29 05:07:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason Baron 2007-06-28 11:56:39 EDT
Description of problem:

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

 remove unused var in alloc_ldt() 

How reproducible:

Steps to Reproduce:
This is very simple. The 4g4g patch removes all the accesses to the
'oldsize' variable in alloc_ldt(), except one now useless assignment and the
variable declaration. This patch fully remove the useless variable.
I test it using the 223851 reproducer which make heavy use of this part of

Actual results:

Expected results:

Additional info:
Comment 1 RHEL Product and Program Management 2007-06-28 12:05:58 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 2 Jason Baron 2007-06-28 15:49:44 EDT
committed in stream U6 build 55.14. A test kernel with this patch is available
from http://people.redhat.com/~jbaron/rhel4/
Comment 3 Jerome Marchand 2007-06-29 05:07:40 EDT

*** This bug has been marked as a duplicate of 234580 ***

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