From: Jens Axboe <axboe@suse.de>
To: John Cherry <cherry@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 1 New compile/sparse warning (overnight build)
Date: Wed, 29 Sep 2004 19:33:43 +0200 [thread overview]
Message-ID: <20040929173343.GF2322@suse.de> (raw)
In-Reply-To: <1096478522.20465.11.camel@cherrybomb.pdx.osdl.net>
On Wed, Sep 29 2004, John Cherry wrote:
> 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))
It's not a new warning, just look at your own generated output:
> 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: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>
The warning simply moved. This should fix it, though.
Signed-off-by: Jens Axboe <axboe@suse.de>
===== fs/bio.c 1.67 vs edited =====
--- 1.67/fs/bio.c 2004-09-28 17:59:14 +02:00
+++ edited/fs/bio.c 2004-09-29 19:34:39 +02:00
@@ -497,7 +497,7 @@
* success
*/
if (!write_to_vm) {
- unsigned long p = uaddr;
+ char __user *p = (char __user *) uaddr;
/*
* for a write, copy in data to kernel pages
@@ -506,7 +506,7 @@
bio_for_each_segment(bvec, bio, i) {
char *addr = page_address(bvec->bv_page);
- if (copy_from_user(addr, (char *) p, bvec->bv_len))
+ if (copy_from_user(addr, p, bvec->bv_len))
goto cleanup;
p += bvec->bv_len;
}
--
Jens Axboe
next prev parent reply other threads:[~2004-09-29 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 17:22 John Cherry
2004-09-29 17:33 ` Jens Axboe [this message]
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=20040929173343.GF2322@suse.de \
--to=axboe@suse.de \
--cc=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®