2005-11-02 kernel 2.6.5 bug fix patch 31 ("April 2004")

If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.

linux-2.6.5-s390-31-april2004.tar.gz / MD5 ... accumulated patch, recommended (2005-11-02)

linux-2.6.5-s390-31-april2004-patches.tar.gz / MD5 ... per-problem-patches, recommended (2005-11-02)

These patches contain the following linux kernel bug fixes:

Description:
kernel: Function 'test_bit' returns non-boolean values.
Symptom:
The system call 'mincore' returns wrong values.
Problem:
The test_bit function returns 0,1,2,4,8,... instead of only 0 or 1. This causes wrong results in mincore syscall.
Solution:
Check for != 0.
Problem-ID:
18894
Description:
kernel: Incorrect PSW check can lead to kernel stack corruption.
Symptom:
Kernel hangs/crashes under rare conditions.
Problem:
When an asynchronous interruption occurs during the execution of the 'critical section' within the generic interruption handling code (entry.S), a faulty check for a userspace PSW may result in a corrupted kernel stack pointer which results in a system hang/crash.
Solution:
Fix userspace PSW check.
Problem-ID:
18809
Description:
kernel: Remove PAGEX pseudo page fault code.
Symptom:
Kernel crashes or kernel stack overflow messages if Linux is running on an old z/VM that does not have pfault support.
Problem:
The system call speedup code introduced a problem in regard to the old PAGEX pseudo page fault interface with z/VM. With the system call speedup code a CPU now enters the kernel with a PSW mask that is enabled for interrupts. The I/O enable bit is used by the PAGEX code to decide if a pseudo page fault may be delivered. Since the system call handler now runs enabled it can get pseudo page fault program checks if the memory for the kernel stack or the CPU lowcore has been evicted by z/VM. If the system call handler is interrupted by a PAGEX exception before the kernel stack has been set up, the user space content of r15 is used to access memory.
Solution:
Remove PAGEX pseudo page fault code. Newer versions of z/VM have the improved pfault pseudo page fault interface which does not have this problem and it replaces the PAGEX interface. To fix the PAGEX pseudo page fault interface would require to add code to the program check handler which would make it slower.
Problem-ID:
18679
Note:
applicable for 31-bit Linux, only
Description:
qeth: OSA for NCP recovery failure
Symptom:
NCP-traffic stop after qeth recovery.
Problem:
qeth does not invoke dev_close() / dev_open() during recovery; just a qeth_stop() / qeth_close() is invoked. Therefore in case of an OSN-device the CCL-kernel-component NDH is not notified of the recovery. Even though qeth recovery is successful, NDH can not react appropriately.
Solution:
For recovery of OSN-devices dev_close() is invoked instead of qeth_stop(), and dev_open() is invoked instead of qeth_open().
Problem-ID:
18603
Description:
qeth: Traffic hang due to missing outstanding PCI on output queue.
Symptom:
Some AWM workloads stop working on OSD chpids, the same applies to NCP traffic on OSN chpids.
Problem:
===> no_pci
===> no invocation of qeth_qdio_output_handler()
===> queued send requests are never flushed
Solution:
Flush buffer even with one network frame included in packed mode when no PCI flag is out anymore.
Problem-ID:
19357
Description:
vmcp: Kernel crash after long vmcp command.
Symptom:
The kernel crashes after long vmcp commands have been entered.
Problem:
The cpcmd buffer was too small to hold long commands.
Solution:
Increase the buffer size to the specified maximum.
Problem-ID:
19349
Description:
z90crypt: CEX2A cards are offlined with certain messages.
Symptom:
CEX2A cards will all go offline until they are reset.
Problem:
Incorrectly handling edge case when talking to CEX2A.
Solution:
Check the proper variable which determines which message format is needed.
Problem-ID:
19040
Description:
zfcp: FCP adapter is re-opened during adapter firmware update.
Symptom:
The FCP adapter is recovered in a wrong way when an unsolicited status LINK_DOWN arrives with subtype FIRMWARE_UPDATE.
Problem:
By receiving of unsolicited status LINK_DOWN with subtype FIRMWARE_UPDATE the payload is analyzed as if it would contain a link down info block.
Solution:
Do not show in payload in such a case but run the usual recovery.
Problem-ID:
19172

Everybody should apply this patch.

To create the complete linux kernel sources, the following patches need to be applied in sequence:

linux-2.6.5.tar.gz (see www.kernel.org/pub/linux/kernel/v2.6)
+ linux-2.6.5-s390-base-april2004.diff (IBM)
+ linux-2.6.5-s390-01-april2004.diff (IBM)
+ xipfs612 (see linuxvm.org/patches/index.html)
+ xipfs622 (see linuxvm.org/patches/index.html)
+ linux-2.6.5-s390-02-april2004.diff (IBM)
+ linux-2.6.5-s390-03-april2004.diff (IBM)
+ single threaded workqueue patch (see marc.theaimsgroup.com/?l=bk-commits-head&m=108305028322900&q=raw)
+ linux-2.6.5-s390-04-april2004.diff (IBM)
+ linux-2.6.5-s390-05-april2004.diff (IBM)
+ linux-2.6.5-s390-06-april2004.diff (IBM)
+ linux-2.6.5-s390-07-april2004.diff (IBM)
+ linux-2.6.5-s390-08-april2004.diff (IBM)
+ linux-2.6.5-s390-09-april2004.diff (IBM)
+ linux-2.6.5-s390-10-april2004.diff (IBM)
+ linux-2.6.5-s390-11-april2004.diff (IBM)
+ linux-2.6.5-s390-12-april2004.diff (IBM)
+ linux-2.6.5-s390-13-april2004.diff (IBM)
+ linux-2.6.5-s390-14-april2004.diff (IBM)
+ linux-2.6.5-s390-15-april2004.diff (IBM)
+ linux-2.6.5-s390-16-april2004.diff (IBM)
+ linux-2.6.5-s390-17-april2004.diff (IBM)
+ linux-2.6.5-s390-18-april2004.diff (IBM)
+ linux-2.6.5-s390-19-april2004.diff (IBM)
+ linux-2.6.5-s390-20-april2004.diff (IBM)
linux-2.6.5-s390-21-april2004.diff (IBM)
+ linux-2.6.5-s390-22-april2004.diff (IBM)
+ linux-2.6.5-s390-23-april2004.diff (IBM)
+ linux-2.6.5-s390-24-april2004.diff (IBM)
+ linux-2.6.5-s390-25-april2004.diff (IBM)
+ linux-2.6.5-s390-26-april2004.diff (IBM)
+ linux-2.6.5-s390-27-april2004.diff (IBM)
+ linux-2.6.5-s390-28-april2004.diff (IBM)
+ linux-2.6.5-s390-29-april2004.diff (IBM)
+ linux-2.6.5-s390-30-april2004.diff (IBM)
+ linux-2.6.5-s390-31-april2004.diff (IBM)

Contact the IBM team

If you want to contact the Linux on System z IBM team refer to the Contact the Linux on System z IBM team page.