linux-kernel - generic bool and sparse errors?

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

Date:	Wed, 06 Jun 2007 11:29:30 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	Al Viro <viro@....linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Josh Triplett <josh@...edesktop.org>
Subject: generic bool and sparse errors?

I'm experimenting with using the generic bool type and using sparse I get tons 
of these messages:

warning: incorrect type in argument 4 (different signedness)
     expected bool [unsigned] [usertype] *[unsigned] success
     got bool *<noident>

I'm not really worried about this, I assume that sparse hasn't caught up with 
what bool really means, but perhaps this can be looked into by someone who knows 
sparse well. The warnings don't really add up and with more people switching to 
use the generic bool this may beceome unwanted.

alternatively we might need to reconsider the `typedef _Bool bool;` declaration 
and force it to be unsigned. I'm not sure what to think of that.

Cheers,

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