linux-kernel - Re: 2.6.19-rc4: known unfixed regressions (v3)

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: <4550B22C.1060307@serpentine.com>
Date:	Tue, 07 Nov 2006 08:19:56 -0800
From:	Bryan O'Sullivan <bos@...pentine.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Adrian Bunk <bunk@...sta.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-rc4: known unfixed regressions (v3)

Eric W. Biederman wrote:

> How comes the driver fixes in the context of my patches?

The fix is simple enough, it's just not as clean as I'd like.  I have to 
pull apart the contents of the ht_irq_msg that the new update hook is 
getting passed, in order to get the vector out, so that I can reprogram 
the offending chip register after I've done the config space writes. 
It's a pretty roundabout way to do the job.

	<b
-
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/