The patch titled
Sky Cpu and Nexus: check for create_proc_entry ret code
has been removed from the -mm tree. Its filename was
sky-cpu-and-nexus-check-for-create_proc_entry-ret-code.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: Sky Cpu and Nexus: check for create_proc_entry ret code
From: Cyrill Gorcunov <[EMAIL PROTECTED]>
Adds checking of create_proc_entry call to prevent possible NULL pointer
usage.
Signed-off-by: Cyrill Gorcunov <[EMAIL PROTECTED]>
Cc: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
Cc: Paul Mackerras <[EMAIL PROTECTED]>
Cc: Kumar Gala <[EMAIL PROTECTED]>
Cc: Brian Waite <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
drivers/misc/hdpuftrs/hdpu_nexus.c | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff -puN
drivers/misc/hdpuftrs/hdpu_nexus.c~sky-cpu-and-nexus-check-for-create_proc_entry-ret-code
drivers/misc/hdpuftrs/hdpu_nexus.c
---
a/drivers/misc/hdpuftrs/hdpu_nexus.c~sky-cpu-and-nexus-check-for-create_proc_entry-ret-code
+++ a/drivers/misc/hdpuftrs/hdpu_nexus.c
@@ -78,10 +78,20 @@ static int hdpu_nexus_probe(struct platf
}
hdpu_slot_id = create_proc_entry("sky_slot_id", 0666, &proc_root);
- hdpu_slot_id->read_proc = hdpu_slot_id_read;
+ if (!hdpu_slot_id) {
+ printk(KERN_WARNING "sky_nexus: "
+ "Unable to create proc dir entry: sky_slot_id\n");
+ } else {
+ hdpu_slot_id->read_proc = hdpu_slot_id_read;
+ }
hdpu_chassis_id = create_proc_entry("sky_chassis_id", 0666, &proc_root);
- hdpu_chassis_id->read_proc = hdpu_chassis_id_read;
+ if (!hdpu_chassis_id) {
+ printk(KERN_WARNING "sky_nexus: "
+ "Unable to create proc dir entry: sky_chassis_id\n");
+ } else {
+ hdpu_chassis_id->read_proc = hdpu_chassis_id_read;
+ }
return 0;
}
_
Patches currently in -mm which might be from [EMAIL PROTECTED] are
git-cifs.patch
git-powerpc.patch
udf-code-style-fixup-v3.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
