linux-kernel - Re: [PATCH 9/9] mISDN: fix sparse 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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <154e089b0812110541x26534df0k47b320f54759df8e@mail.gmail.com>
Date:	Thu, 11 Dec 2008 14:41:34 +0100
From:	"Hannes Eder" <hannes@...neseder.net>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Karsten Keil" <kkeil@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 9/9] mISDN: fix sparse warnings

On Wed, Dec 10, 2008 at 6:08 PM, Andi Kleen <andi@...stfloor.org> wrote:
> Hannes Eder <hannes@...neseder.net> writes:
>> @@ -918,7 +919,7 @@ hfcmulti_resync(struct hfc_multi *locked, struct hfc_multi *newmaster, int rm)
>>       /* Disable sync of all cards */
>>       list_for_each_entry_safe(hc, next, &HFClist, list) {
>>               if (test_bit(HFC_CHIP_PLXSD, &hc->chip)) {
>> -                     plx_acc_32 = (u_int *)(hc->plx_membase+PLX_GPIOC);
>> +                     plx_acc_32 = (u_int __iomem *)(hc->plx_membase+PLX_GPIOC);
>
> It would be probably better to declare plx_membase __iomem too instead
> of so much casting.

it is, but of type "u_char __iomem *" (after applying this patch):

+       u_char __iomem  *pci_membase; /* PCI memory (MUST BE BYTE POINTER) */

so thats why we need the cast.

What if we declare plx_acc_32 of type "u_char __iomem *", or both as
"void __iomem *"?
I slightly favor the later, against the LOUD comment.

If plx_membase is declared without __iomem the cast "(u_int __iomem*)" produces
a warning "cast adds address space to expression"

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