linux.git/drivers/s390/block, branch v2.6.31

[S390] drivers/s390: put NULL test before dereference

2009-08-23T16:10:00+00:00

If the NULL test on block is needed, it should be before the dereference of
the base field.

The semantic match that finds this problem is as follows:
(http://coccinelle.lip6.fr/)

// 
@r@
expression E1,E2;
identifier fld;
statement S1,S2;
@@

E1 = E2->fld;
(
if (E1 == NULL) S1 else S2
|
*if (E2 == NULL) S1 else S2
)
// 

Signed-off-by: Julia Lawall 
Signed-off-by: Martin Schwidefsky

headers: smp_lock.h redux

2009-07-12T19:22:34+00:00

* Remove smp_lock.h from files which don't need it (including some headers!)
* Add smp_lock.h to files which do need it
* Make smp_lock.h include conditional in hardirq.h
  It's needed only for one kernel_locked() usage which is under CONFIG_PREEMPT

  This will make hardirq.h inclusion cheaper for every PREEMPT=n config
  (which includes allmodconfig/allyesconfig, BTW)

Signed-off-by: Alexey Dobriyan 
Signed-off-by: Linus Torvalds

[S390] improve suspend/resume error messages

2009-07-07T14:37:53+00:00

From: Michael Holzheu 

Signed-off-by: Michael Holzheu 
Signed-off-by: Christian Borntraeger 
Signed-off-by: Martin Schwidefsky

[S390] dasd: correct debugfeature sense dump

2009-07-07T14:37:52+00:00

remove loop, add some debug data and use get_sense function

Signed-off-by: Stefan Haberland 
Signed-off-by: Martin Schwidefsky

[S390] dasd: fix refcounting in dasd_change_state

2009-06-22T10:08:23+00:00

To set a dasd online dasd_change_state is called twice. The first
cycle will schedule initial analysis of the device, set the rc to
-EAGAIN and will not touch the device state any more.
The initial analysis will in turn call dasd_change_state to increase
the state to the final DASD_STATE_ONLINE.

If the dasd_change_state on the second thread outruns the other one
both finish with the state set to DASD_STATE_ONLINE and the device
refcount will be decreased by 2.

Fix this by leaving dasd_change_state on rc == -EAGAIN so that the
refcount will always be decreased by 1.

Signed-off-by: Sebastian Ott 
Signed-off-by: Martin Schwidefsky

[S390] dasd_pm: fix stop flag handling

2009-06-22T10:08:22+00:00

The stop flags are handled in the generic restore function so the
stop flag is removed also for FBA and DIAG devices.

Signed-off-by: Stefan Haberland 
Signed-off-by: Martin Schwidefsky

[S390] pm: dcssblk power management callbacks.

2009-06-16T08:31:22+00:00

Signed-off-by: Gerald Schaefer 
Signed-off-by: Martin Schwidefsky

[S390] pm: xpram driver power management callbacks

2009-06-16T08:31:11+00:00

Signed-off-by: Michael Holzheu 
Signed-off-by: Martin Schwidefsky

[S390] pm: dasd power management callbacks.

2009-06-16T08:31:10+00:00

Introduce the power management callbacks to the dasd driver. On suspend
the dasd devices are stopped and removed from the focus of alias
management.
On resume they are reinitialized by rereading the device characteristics
and adding the device to the alias management.
In case the device has gone away during suspend it will caught in the
suspend state with stopped flag set to UNRESUMED. After it appears again
the restore function is called again.

Signed-off-by: Stefan Haberland 
Signed-off-by: Martin Schwidefsky

[S390] dasd: forward internal errors to dasd_sleep_on caller

2009-06-12T08:27:36+00:00

If a DASD requests is started with dasd_sleep_on and fails, then the
calling function may need to know the reason for the failure.
In cases of hardware errors it can inspect the sense data in the irb,
but when the reason is internal (e.g. start_IO failed) then it needs
a meaningfull return code.

Signed-off-by: Stefan Weinhuber 
Signed-off-by: Martin Schwidefsky