From: John Cherry <cherry@osdl.org>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 1 New compile/sparse warning (overnight build)
Date: Wed, 29 Sep 2004 10:22:03 -0700 [thread overview]
Message-ID: <1096478522.20465.11.camel@cherrybomb.pdx.osdl.net> (raw)
This sparse warning was introduced with patch 1.2000 (axboe).
In fs/bio.c (line 509),
if (copy_from_user(addr, (char *) p, bvec->bv_len))
should probably be
if (copy_from_user(addr, (char __user *) p, bvec->bv_len))
John
--------------------------------------------------------------
Compiler: gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Arch: i386
Summary:
New warnings = 1
Fixed warnings = 3
New warnings:
-------------
fs/bio.c:509:30: warning: incorrect type in argument 2 (different
address spaces)
fs/bio.c:509:30: expected void const [noderef] *from<asn:1>
fs/bio.c:509:30: got char *<noident>
Fixed warnings:
---------------
fs/bio.c:392:20: warning: incorrect type in argument 1 (different
address spaces)
fs/bio.c:392:20: expected void [noderef] *to<asn:1>
fs/bio.c:392:20: got char *uaddr
fs/bio.c:462:31: warning: incorrect type in argument 2 (different
address spaces)
fs/bio.c:462:31: expected void const [noderef] *from<asn:1>
fs/bio.c:462:31: got char *<noident>
kernel/sys.c:1737:34: warning: incorrect type in argument 2 (different
address spaces)
kernel/sys.c:1737:34: expected char const [noderef] *src<asn:1>
kernel/sys.c:1737:34: got char *<noident>
next reply other threads:[~2004-09-29 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 17:22 John Cherry [this message]
2004-09-29 17:33 ` Jens Axboe
2004-09-29 17:51 ` John Cherry
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=1096478522.20465.11.camel@cherrybomb.pdx.osdl.net \
--to=cherry@osdl.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®