linux.git/drivers/message/i2o, branch v2.6.23

fix integer overflow warning in i2o_block

2007-07-31T22:39:44+00:00

drivers/message/i2o/i2o_block.c: In function 'i2o_block_transfer':
drivers/message/i2o/i2o_block.c:837: warning: integer overflow in expression

msg->u.head[1] = cpu_to_le32(I2O_CMD_PRIVATE << 24 | HOST_TID << 12 | tid);
and I2O_CMD_PRIVATE is defined as 0xFF.  This gets "0xFF0100 | tid" and fits
into 32-bit unsigned but not into 32-bit signed integer properly.  Target
value is defined as u32 so the claculation does not fit during computation.

Change local variable tid to u32 so the whole expression is of u32 type and
fits well into u32 result.

Signed-off-by: Meelis Roos 
Cc: "Salyzyn, Mark" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[BLOCK] Get rid of request_queue_t typedef

2007-07-24T07:28:11+00:00

Some of the code has been gradually transitioned to using the proper
struct request_queue, but there's lots left. So do a full sweet of
the kernel and get rid of this typedef and replace its uses with
the proper type.

Signed-off-by: Jens Axboe

mm: Remove slab destructors from kmem_cache_create().

2007-07-20T01:11:58+00:00

Slab destructors were no longer supported after Christoph's
c59def9f222d44bb7e2f0a559f2906191a0862d7 change. They've been
BUGs for both slab and slub, and slob never supported them
either.

This rips out support for the dtor pointer from kmem_cache_create()
completely and fixes up every single callsite in the kernel (there were
about 224, not including the slab allocator definitions themselves,
or the documentation references).

Signed-off-by: Paul Mundt

i2o debug output cleanup

2007-07-17T17:23:06+00:00

Fix output of i2o debug messages, extra KERN_ are removed.

Signed-off-by: Vasily Averin 
Acked-by: Alan Cox 
Cc: Markus Lidel 
Acked-by: Kirill Korotaev 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

i2o proc reading oops

2007-07-17T17:23:06+00:00

Fix oops on reading from some i2o proc files (i2o_seq_show_driver_store() and
other) because their handlers uses "exec" field in struct i2o_controller

Signed-off-by: Vasily Averin 
Acked-by: Alan Cox 
Cc: Markus Lidel 
Acked-by: Kirill Korotaev 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

i2o message leak in i2o_msg_post_wait_mem()

2007-07-17T17:23:06+00:00

We need to free i2o msg in case of error.

Signed-off-by: Vasily Averin 
Acked-by: Alan Cox 
Cc: Markus Lidel 
Acked-by: Kirill Korotaev 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

wrong memory access in i2o_block_device_lock()

2007-07-17T17:23:06+00:00

This patch fixes access to memory that has not been allocated:
i2o_msg_get_wait() can returns errors different from I2O_QUEUE_EMPTY.  But the
result is checked only against this code.  If it is not I2O_QUEUE_EMPTY then
we dereference the error code as the pointer later.

Signed-off-by: Vasily Averin 
Acked-by: Alan Cox 
Cc: Markus Lidel 
Acked-by: Kirill Korotaev 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

i2o_cfg_passthru cleanup

2007-07-17T17:23:06+00:00

This patch fixes a number of issues in i2o_cfg_passthru{,32}:
- i2o_msg_get_wait() return vaile is not checked;
- i2o_message memory leaks on error paths;
- infinite loop to sg_list_cleanup in passthru32

It's important issue because of i2o_cfg_passthru is used by raidutils for
monitorig controllers state, and in case of memory shortage it leads to the
node crash or disk IO stall.

[akpm@linux-foundation.org: fix null-ptr deref]
Signed-off-by: Vasily Averin 
Acked-by: Alan Cox 
Cc: Markus Lidel 
Acked-by: Kirill Korotaev 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Introduce CONFIG_VIRT_TO_BUS

2007-07-16T16:05:42+00:00

Make some offending drivers depend on it and set CONFIG_ARCH_NO_VIRT_TO_BUS
for ppc64 so that we don't build those drivers.

This gets PowerPC allmodconfig and allyesconfig much closer to building.

Signed-off-by: Stephen Rothwell 
Cc: Al Viro 
Acked-by: David Miller 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Use mutexes instead of semaphores in I2O driver

2007-07-16T16:05:41+00:00

The I2O driver uses two semaphores as mutexes.  Use the mutex API instead of
the (binary) semaphores.

Signed-off-by: Matthias Kaehlcke 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds