 |

Kernel 2.4 based: June 2003 stream
|
 |
|
 |
|
jump to next patch
jump
to xref jump to Download
Area
If you download any software from this web site please be aware of the
Warranty Disclaimer and Limitation of Liabilities.
linux-2.4.21-s390-04-june2003.tar.gz
/ MD5 ... accumulated patch, recommended (2003-08-28)
linux-2.4.21-s390-04-june2003-patches.tar.gz
/ MD5 ... per-problem-patches, recommended (2003-08-28)
These patches contain the following linux kernel bug fixes:
| Description: |
dasd_diag: buggy CMS label recognition in
fs/partitions/ibm.c |
| Symptom: |
CMS reserved minidisk detection doesn't work as expected |
| Problem: |
CMS label is read from page, that had been freed before |
| Solution: |
no longer use freed storage for CMS label recognition |
| Problem-ID: |
3611 |
| Description: |
zfcp: erroneous and inconsistent strings in user interface |
| Symptom: |
N_Port IDs might be truncated to half of their length;
no fixed format/length of WWPNs, FCP_LUNs, ...;
varying spellings of FCP_LUN, SCSI ID, ...; |
| Problem: |
missing convention on spellings and formats |
| Solution: |
corrected strings and formats |
| Problem-ID: |
3531 |
| Description: |
zfcp: don't forget to shutdown some adapters |
| Symptom: |
zfcp bug messages about buffers being still in use on module
unload or system shutdown (see console or /var/log/messages), IRQ
of some FCP subchannels are not released after removal of zfcp
module (see /proc/subchannels), failure of zfcp to setup those IRQs
and use corresponding subchannels after module reload |
| Problem: |
While all FCP adapters configured in the zfcp map are always
set up, only those successfully registered with the SCSI stack are
shutdown as this was done in a SCSI stack callback into zfcp for
each registered and to be unregistered SCSI host. In case of a
failed registration of an adapter with the Linux SCSI stack (e.g.
low on memory conditions) some adapters might never be
shutdown. |
| Solution: |
don't rely on the SCSI stack's notion of the set of to be
shutdown FCP subchannels but do adapter shutdown in a different
place where all adapters are guaranteed to be halted properly |
| Problem-ID: |
3620 |
| Description: |
zfcp: error recovery stall in case of unavailable
nameserver |
| Symptom: |
modprobe hangs if nameserver port is inaccessible |
| Problem: |
error recovery is infinitely waiting for the completion of the
'nameserver open' action which was not issued at all because the
nameserver port was already known to be inaccessible and thus had
been marked as failed |
| Solution: |
fail 'open port' action immediately if issueing an 'open
nameserver port' action is not possible though required |
| Problem-ID: |
3615 |
| Description: |
zfcp: error recovery escalation in case of unavailable
nameserver |
| Symptom: |
re-establishing of port connections (even working ones) and
re-initialization of adapter connection, which is disruptive to
ongoing SCSI I/O, if the nameserver port is inaccessible |
| Problem: |
recovery escalation regardless of the fact that it can't
succeed in this particular case |
| Solution: |
propagate 'failed' status of nameserver port to other ports
requiring a nameserver lookup when being opened |
| Problem-ID: |
3617 |
| Description: |
Missing CVS version in z90crypt. |
| Symptom: |
n/a |
| Problem: |
Can't figure out CVS version a given z90crypt driver was built
from. |
| Solution: |
Store versions of z90common.h z90crypt.h z90hardware.c and
z90main.c in a global char array "version" |
| Problem-ID: |
n/a |
| Description: |
Pseudo-random number generation is not secure |
| Symptom: |
z90crypt_read returns predictable numbers |
| Problem: |
Each call to z90crypt_read requires additional entropy |
| Solution: |
In s390_ksyms, externalize the function urandom_read in
z90main, replace the current pseudo-random number generation code
with a call to urandom-read |
| Problem-ID: |
4096 |
| Description: |
crash when using ctc tty with gcov |
| Symptom: |
see description! |
| Problem: |
Invalid use of netif_stop_queue() and netfi_wake_queue() for
ctc ttys |
| Solution: |
code fixed |
| Problem-ID: |
n/a |
Everybody should apply this patch.
To create the complete linux kernel sources, the following
patches need to be applied in sequence:
linux-2.4.21.tar.gz (see www.kernel.org)
+ linux-2.4.21-s390-june2003.diff (IBM)
+ linux-2.4.21-s390-01-june2003.diff (IBM)
+ linux-2.4.21-s390-02-june2003.diff (IBM)
+ linux-2.4.21-s390-03-june2003.diff (IBM)
+ linux-2.4.21-s390-04-june2003.diff (IBM)
Note: If On-demand timer is required, apply as last patch:
+ linux-2.4.21-s390-timer-01-june2003.diff (IBM)
|
|
 |
|
 |