The patch titled
fs/bio.c: add missing __user annotation
has been added to the -mm tree. Its filename is
fs-bioc-add-missing-__user-annotation.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: fs/bio.c: add missing __user annotation
From: Michal Simek <monstr@xxxxxxxxx>
As reported by sparse:
fs/bio.c:720:13: warning: incorrect type in assignment (different address spaces)
fs/bio.c:720:13: expected char *iov_addr
fs/bio.c:720:13: got void [noderef] <asn:1>*
fs/bio.c:724:36: warning: incorrect type in argument 2 (different address spaces)
fs/bio.c:724:36: expected void const [noderef] <asn:1>*from
fs/bio.c:724:36: got char *iov_addr
Signed-off-by: Michal Simek <monstr@xxxxxxxxx>
Cc: Jens Axboe <jens.axboe@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/bio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/bio.c~fs-bioc-add-missing-__user-annotation fs/bio.c
--- a/fs/bio.c~fs-bioc-add-missing-__user-annotation
+++ a/fs/bio.c
@@ -721,7 +721,7 @@ static int __bio_copy_iov(struct bio *bi
while (bv_len && iov_idx < iov_count) {
unsigned int bytes;
- char *iov_addr;
+ char __user *iov_addr;
bytes = min_t(unsigned int,
iov[iov_idx].iov_len - iov_off, bv_len);
_
Patches currently in -mm which might be from monstr@xxxxxxxxx are
origin.patch
fs-remove-sparse-errors-in-proc_devtreec.patch
fs-bioc-add-missing-__user-annotation.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
