linux-kernel - Re: [Bug #10669] ACPI: kmemcheck: Caught 16-bit read from freed memory (f7c12ec6)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19f34abd0806071458l407a86abt40edf943f54f5e03@mail.gmail.com>
Date:	Sat, 7 Jun 2008 23:58:43 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>,
	"Lin Ming" <ming.m.lin@...el.com>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [Bug #10669] ACPI: kmemcheck: Caught 16-bit read from freed memory (f7c12ec6)

On Sat, Jun 7, 2008 at 10:42 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> This message has been generated automatically as a part of a report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.25.  Please verify if it still should be listed.
>
>
> Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=10669
> Subject         : ACPI: kmemcheck: Caught 16-bit read from freed memory (f7c12ec6)
> Submitter       : Vegard Nossum <vegard.nossum@...il.com>
> Date            : 2008-05-06 16:09 (33 days old)
> References      : http://marc.info/?l=linux-acpi&amp;m=121009034825514&amp;w=4
> Handled-By      : Lin Ming <ming.m.lin@...el.com>
>                  Ming Lin <ming.m.lin@...el.com>
> Patch           : http://bugzilla.kernel.org/attachment.cgi?id=16199&amp;action=view
>

I'm sorry, I have no idea why this fix isn't going upstream. I tested
the patch and it's completely fine with regards to kmemcheck. And the
patch it fixes was already upstream so I don't see what's stopping it
from going back in + the fix.

So the question is if this should go in now, or whether it should wait
till 2.6.26. In either case, the regression itself was solved by the
means of a revert, and that's quite a long time ago, so the current
kernel should be fine in this regard, though I think the original
patch fixed some errors on its own.

Ming Lin, will you resubmit the original patch plus the fix for
re-inclusion in mainline? There's no point in having this regression
entry around when it has been fixed by either/both the revert or/and
the extra "fix" patch.

Thanks! :-)

Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/