linux-kernel - pci_read_config_* functions and uninitialized warnings?

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>] [day] [month] [year] [list]

Message-Id: <E749C9B9-2E83-4F54-A1C8-CBF376ECBD57@gmail.com>
Date:	Wed, 19 Nov 2008 11:15:32 -0700
From:	Richard Holden <aciddeath@...il.com>
To:	linux-next@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: pci_read_config_* functions and uninitialized warnings?

I'm building linux-next and seeing a lot of uninitialized warnings  
that go back to values being set using pci_read_config_* functions.  
Does anyone more familiar than I am with that code have any ideas on  
how to get GCC to realize that the pci_read_config_* initialize the  
vars. I don't want to end up submitting a lot of patches with  
uninitialized_var to fix the problems.

gcc --version: gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.1)

-Richard Holden
--
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/