The patch titled
I2O: handle __copy_from_user
has been added to the -mm tree. Its filename is
i2o-handle-__copy_from_user.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: I2O: handle __copy_from_user
From: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Handle __copy_from_user() return value.
Noticed by inspection, not from build warning.
Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx>
Cc: Markus Lidel <Markus.Lidel@xxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
drivers/message/i2o/i2o_config.c | 6 +++++-
1 files changed, 5 insertions(+), 1 deletion(-)
diff -puN drivers/message/i2o/i2o_config.c~i2o-handle-__copy_from_user drivers/message/i2o/i2o_config.c
--- a/drivers/message/i2o/i2o_config.c~i2o-handle-__copy_from_user
+++ a/drivers/message/i2o/i2o_config.c
@@ -265,7 +265,11 @@ static int i2o_cfg_swdl(unsigned long ar
return -ENOMEM;
}
- __copy_from_user(buffer.virt, kxfer.buf, fragsize);
+ if (__copy_from_user(buffer.virt, kxfer.buf, fragsize)) {
+ i2o_msg_nop(c, msg);
+ i2o_dma_free(&c->pdev->dev, &buffer);
+ return -EFAULT;
+ }
msg->u.head[0] = cpu_to_le32(NINE_WORD_MSG_SIZE | SGL_OFFSET_7);
msg->u.head[1] =
_
Patches currently in -mm which might be from randy.dunlap@xxxxxxxxxx are
origin.patch
debugfs-add-header-file.patch
git-acpi.patch
korg1212-fix-printk-format-warning.patch
cpufreq-select-consistently-re-2619-rc5-mm1.patch
git-ieee1394.patch
git-infiniband.patch
mtd-fix-printk-format-warning.patch
git-ocfs2.patch
parisc-fix-module_param-iommu-permission.patch
fuse-fix-compile-without-config_block.patch
tifm-fix-null-ptr-and-style.patch
kconfig-printk_time-depends-on-printk.patch
i2o-handle-__copy_from_user.patch
generic-bug-implementation-handle-bug=n.patch
visws-sgivwfb-is-module-needs-exports.patch
extend-notifier_call_chain-to-count-nr_calls-made-fixes.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
