| 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
| ||
|
Message-ID: <20070725192422.47c7c476@osprey.hogchain.net> Date: Wed, 25 Jul 2007 19:24:22 -0500 From: Jay Cliburn <jacliburn@...lsouth.net> To: Chuck Ebbert <cebbert@...hat.com> Cc: Chris Snook <csnook@...hat.com>, Netdev <netdev@...r.kernel.org>, jeff@...zik.org, Huang Xiong <xiong.huang@...eros.com> Subject: Re: atl1 driver corrupting memory? On Wed, 25 Jul 2007 17:31:02 -0400 Chuck Ebbert <cebbert@...hat.com> wrote: > This is what was committed. > > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=3f516c00d416bd39aab6cfb348b68919e295fe23 > http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ef76e3e2505db01f7d4b537854f4a177220c26c8 I'm doubtful these patches will fix the highmem corruption problem we've seen in the L1. I actually extracted the changes in the referenced commits from the vendor's current out-of-tree driver, and unfortunately he was able to duplicate the problem in his lab using that driver. As a workaround, Chuck, your reporter can boot with mem=3900 until the problem is resolved. I go on record with Chris: we should apply the patch at http://lkml.org/lkml/2007/6/25/293 until we get to the bottom of it. The patch is in Jeff's queue, but I think he suspects a driver bug and so far hasn't chosen to apply the patch. Jeff, can we ask you to please reconsider? Jay - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists