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: <Pine.LNX.4.64.0611071258220.8122@topaz.pathscale.com>
Date:	Tue, 7 Nov 2006 13:01:44 -0800 (PST)
From:	Dave Olson <olson@...hscale.com>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Bryan O'Sullivan <bos@...pentine.com>,
	Adrian Bunk <bunk@...sta.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-rc4: known unfixed regressions (v3)

On Tue, 7 Nov 2006, Eric W. Biederman wrote:
| > Displaying something that might change is a fact of life, and no
| > different than the PCI world.  It's still best to keep things as
| > correct as possible.
| 
| No.  I was thinking of the rat hole in pci config space you have to
| access to read these registers.  You have to actively write a pci
| config value to select which register you are going to read.
| 
| So by default it is not safe to touch this value from user space,
| because you could mess up the kernel, if the kernel is updating the
| value.

Nonetheless, as root, lspci already does that (it displays the MSI
interrupt info).  I  wasn't talking about fixing that, just saying
that having the data being as correct as possible, is highly
desirable.   We can't know everything that everybody is doing with
the data.

Improvements in the pciutils library and locking with respect to the
kernel may well be desirable, but are an independent issue from
correctness.

Dave Olson
dave.olson@...gic.com
-
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/