From: Randy Dunlap <rdunlap@xenotime.net>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: linux kernel warnings/errors
Date: Tue, 23 Feb 2010 14:20:49 -0800 [thread overview]
Message-ID: <4B8454C1.6010402@xenotime.net> (raw)
In-Reply-To: <20100223205942.GA32491@feather>
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
On 02/23/10 12:59, Josh Triplett wrote:
> On Tue, Feb 23, 2010 at 11:49:06AM -0800, Randy Dunlap wrote:
>> Hi,
>>
>> You probably know that sparse produces a ton of errors & warnings when
>> run on the Linux kernel tree (a little over 1 MB in my latest 'make C=1'
>> on x86_64 arch.).
>>
>> I'm wondering if all of these are valid.
>>
>> Examples:
>>
>>
>> 1. Use of the BUILD_BUG_ON() macro causes this error from sparse:
>>
>> arch/x86/kernel/paravirt.c:101:9: error: invalid bitfield width, -1.
>>
>> include/linux/kernel.h:
>>
>> /* Force a compilation error if condition is true */
>> #define BUILD_BUG_ON(condition) ((void)BUILD_BUG_ON_ZERO(condition))
>>
>> /* Force a compilation error if condition is true, but also produce a
>> result (of value 0 and type size_t), so the expression can be used
>> e.g. in a structure initializer (or where-ever else comma expressions
>> aren't permitted). */
>> #define BUILD_BUG_ON_ZERO(e) (sizeof(struct { int:-!!(e); }))
>
> In theory that should only happen if the BUILD_BUG_ON_ZERO actually
> triggers, and thus sparse fails to build just as GCC would. If sparse
> has this problem and GCC doesn't, could you please provide a minimal
> test case?
Sure, attached.
>> 2. drivers/block/drbd/drbd_int.h uses __protected_by(var);
>> this seems to be unknown to sparse.
>>
>> #ifdef __CHECKER__
>> # define __protected_by(x) __attribute__((require_context(x,1,999,"rdwr")))
>>
>> sparse says many times:
>>
>> drivers/block/drbd/drbd_int.h:887:39: error: attribute 'require_context': unknown attribute
>
> That looks broken. A few patches went around for new Sparse
> context-tracking features, one of which got reverted before the 0.4.2
> release, but I don't think any of them would have allowed *that*.
Yeah, I recall seeing some of the context patches.
Thanks.
--
~Randy
[-- Attachment #2: build_bug_on.c --]
[-- Type: text/x-csrc, Size: 713 bytes --]
/* Force a compilation error if condition is true */
#define BUILD_BUG_ON(condition) ((void)BUILD_BUG_ON_ZERO(condition))
/* Force a compilation error if condition is true, but also produce a
result (of value 0 and type size_t), so the expression can be used
e.g. in a structure initializer (or where-ever else comma expressions
aren't permitted). */
#define BUILD_BUG_ON_ZERO(e) (sizeof(struct { int:-!!(e); }))
struct branch {
unsigned char opcode;
int delta;
} __attribute__((packed));
unsigned paravirt_patch_call(void *insnbuf)
{
struct branch *b = insnbuf;
b->opcode = 0xe8; /* call */
b->delta = 0x1234;
BUILD_BUG_ON(sizeof(*b) != 5);
return 5;
}
int main(int argc, char *argv[])
{
}
next prev parent reply other threads:[~2010-02-23 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 19:49 linux kernel warnings/errors Randy Dunlap
2010-02-23 20:59 ` Josh Triplett
2010-02-23 22:20 ` Randy Dunlap [this message]
2010-02-23 22:40 ` linux kernel warnings/errors (#7) Randy Dunlap
2010-02-24 0:55 ` linux kernel warnings/errors (#8) Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B8454C1.6010402@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).