From: Theodore Ts'o <tytso@thunk.org>
To: linux-fsdevel@vger.kernel.org, linux-sparse@vger.kernel.org
Subject: What does this sparse warning mean in posix_acl.h?
Date: Sat, 17 Aug 2013 10:28:22 -0400 [thread overview]
Message-ID: <nsxtxio1jeh.fsf@lambda.thunk.org> (raw)
It apparently has something to do with rcu and "address spaces" but I'm
not completely sure what sparse is complaining about --- and whether it
is a false positive or a bug in the posix_acl.h.
Can someone explain what's going on, and whether it's something to be
concerned about?
Thanks,
- Ted
% ../make-ext4 C=1 fs/ext4/acl.o
make[2]: Nothing to be done for `all'.
GEN /u1/ext4/Makefile
CHK include/generated/uapi/linux/version.h
make[2]: Nothing to be done for `relocs'.
Using /usr/projects/linux/ext4 as source for kernel
CHK include/generated/utsrelease.h
CALL /usr/projects/linux/ext4/scripts/checksyscalls.sh
<stdin>:1220:2: warning: #warning syscall kcmp not implemented [-Wcpp]
<stdin>:1223:2: warning: #warning syscall finit_module not implemented [-Wcpp]
CHECK /usr/projects/linux/ext4/fs/ext4/acl.c
/usr/projects/linux/ext4/include/linux/posix_acl.h:137:9: warning: incorrect type in assignment (different address spaces)
/usr/projects/linux/ext4/include/linux/posix_acl.h:137:9: expected struct posix_acl *<noident>
/usr/projects/linux/ext4/include/linux/posix_acl.h:137:9: got struct posix_acl [noderef] <asn:4>*<noident>
/usr/projects/linux/ext4/include/linux/posix_acl.h:137:9: warning: incorrect type in assignment (different address spaces)
/usr/projects/linux/ext4/include/linux/posix_acl.h:137:9: expected struct posix_acl *<noident>
/usr/projects/linux/ext4/include/linux/posix_acl.h:137:9: got struct posix_acl [noderef] <asn:4>*<noident>
next reply other threads:[~2013-08-17 14:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-17 14:28 Theodore Ts'o [this message]
2013-08-17 16:16 ` What does this sparse warning mean in posix_acl.h? Linus Torvalds
2013-08-17 20:55 ` Theodore Ts'o
2013-08-17 21:14 ` Linus Torvalds
2013-08-17 21:23 ` Theodore Ts'o
2013-08-17 21:31 ` Linus Torvalds
2013-08-17 21:23 ` Linus Torvalds
2013-08-17 16:17 ` Josh Triplett
2013-08-17 16:33 ` Linus Torvalds
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=nsxtxio1jeh.fsf@lambda.thunk.org \
--to=tytso@thunk.org \
--cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.