[patch i2o 3/6] i2o message leak in i2o_msg_post_wait_mem()

We need to free i2o msg in case of error.

Signed-off-by:	Vasily Averin <[email protected]>

--- lk2.6/drivers/message/i2o/exec-osm.c
+++ lk2.6/drivers/message/i2o/exec-osm.c
@@ -131,8 +131,10 @@ int i2o_msg_post_wait_mem(struct i2o_con
 	int rc = 0;

 	wait = i2o_exec_wait_alloc();
-	if (!wait)
+	if (!wait) {
+		i2o_msg_nop(c, msg);
 		return -ENOMEM;
+	}

 	if (tcntxt == 0xffffffff)
 		tcntxt = 0x80000000;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [patch i2o] i2o layer cleanup
    • From: Vasily Averin <[email protected]>

• Prev by Date: [patch i2o 2/6] wrong memory access in i2o_block_device_lock()
• Next by Date: [patch i2o 4/6] i2o proc reading oops
• Previous by thread: [patch i2o 2/6] wrong memory access in i2o_block_device_lock()
• Next by thread: [patch i2o 4/6] i2o proc reading oops
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]