https://bugzilla.novell.com/show_bug.cgi?id=350017

User [EMAIL PROTECTED] added comment
https://bugzilla.novell.com/show_bug.cgi?id=350017#c35


Thomas Renninger <[EMAIL PROTECTED]> changed:

           What    |Removed                                         |Added
----------------------------------------------------------------------------
                 CC|                                                |[EMAIL 
PROTECTED], [EMAIL PROTECTED]




--- Comment #35 from Thomas Renninger <[EMAIL PROTECTED]>  2008-03-05 05:32:07 
MST ---
Puuh.., this patch is very much appreciated.

I went down to dsobject.c, utcopy.c (there I was sure it could be..., etc.). I
still have not checked why this is in utobject.c..., will try do so later.

I tested your patch against 10.3.
The handle is NULL now instead of uninitialized or corrupted.

I tested this (and this was so hard to debug, I had to reboot for each test..)
on an HP machine with a modified DSDT: I removed the passive reference and
replaced it with a undefined one.

Now also evaluate_reference must check against the NULL handle, I will attach
an adjusted patch against 10.3.

Alexey, what do you think. I very much like to add this to 10.3 (not sure about
SLE[SD], we could get problems there also..., hmm when the machine is certified
they have to revert the BIOS breakage, on the other hand we are still in Beta
phase...).
We could trigger NULL pointer accesses with this and cause regressions?

IMO this should go into 11.0 and 2.6.25-rcX get at least some weeks testing and
then possibly back to 10.3?
I already broke cpufreq for a lot 10.3 machines once, I don't want to slip into
something similar again...


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to