Bug 5425 - The copy of Device object to LocalX is not ever released
Summary: The copy of Device object to LocalX is not ever released
Status: REJECTED INVALID
Alias: None
Product: ACPI
Classification: Unclassified
Component: ACPICA-Core (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Lin Ming
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-12 10:25 UTC by Valery A Podrezov
Modified: 2007-11-06 20:24 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
ASL code to reproduce bug. (656 bytes, text/plain)
2005-10-12 10:26 UTC, Valery A Podrezov 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Valery A Podrezov 2005-10-12 10:25:56 UTC 
Most recent kernel where this bug did not occur:
Distribution:
Hardware Environment:
Software Environment:
Problem Description:

The "memory leak" bug.
The issue has been revealed by both PMEMCV and OAS (see bug 5422).
It is a legal ACPI operation copying Device to LocalX.
This operation produces the memory allocation which is not even
released after the method termination and even when it loses all
the references to it and thus becomes an outstanding allocation.

Steps to reproduce:

Run interpreter with the .asl demo code attached below.
Comment 1 Valery A Podrezov 2005-10-12 10:26:55 UTC 
Created attachment 6289 [details]
ASL code to reproduce bug.

The attached demo (m001) produces as many memory leaks
as the length of the While cycle.


INTERNAL BUG NUMBER

   163
Comment 2 Lin Ming 2007-11-06 18:52:11 UTC 
Copy a Device is now not allowable.
The allowable source operands of CopyObject is ARGI_DATAREFOBJ, which can be one of the following:
Integer
String
Buffer
Package
Object Reference
DdbHandle
Comment 3 Lin Ming 2007-11-06 20:24:50 UTC 
Reject, since copy Device is not allowable now.
Note You need to log in before you can comment on or make changes to this bug.