2007-11-20 kernel 2.6.16 bug fix patch 18 ("October 2005")

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

linux-2.6.16-s390-18-october2005.tar.gz / MD5 ... accumulated patch, recommended (2007-11-20)

linux-2.6.16-s390-18-october2005-patches.tar.gz / MD5 ... per-problem-patches, recommended (2007-11-20)

This patch contains the following linux kernel bug fixes:

Description:
qeth: Discard inbound packets with unknown header id.
Symptom:
Kernel panic in qeth_qdio_input_handler.
Problem:
For unsettled reasons an OSA-card may transfer packets with an unknown header id. The qeth driver is aware of 3 types of header ids (layer3, layer2, and osn) and treats packets that are neither layer3 nor layer2 as osn packets, where an skb_push of 32 bytes is necessary.
This skb_push results in a kernel panic if applied to packets with unknown qdio header id.
Solution:
Add debug support for inbound packets with unknown header id and discard them afterwards
Problem-ID:
39323
Description:
cio: Incorrect check for activity in cmf.
Symptom:
Values reported by cmf may be inconsistent.
Problem:
Incorrect check for activity in cmf_copy_block().
Solution:
Fix brackets in activity check.
Problem-ID:
39542
Description:
cio: Change device sense procedure to work with PAV aliases.
Symptom:
PAV alias DASDs can not be set online.
Problem:
SMR CCWs are rejected by DASD alias devices until all paths of the base device are grouped.
Solution:
Remove SMR before SNSID.
Problem-ID:
40296
Description:
kernel: Enhance re-boot time of z/VM guests.
Symptom:
Re-boot of large z/VM guests takes a lot of time.
Problem:
IPL is done without the CLEAR option. Therefore z/VM can not release the memory pages at boot time, which leads to the slow reboot.
Solution:
Use 'IPL CLEAR' for re-ipl under z/VM.
Problem-ID:
38321
Description:
kernel: pfault disabled.
Symptom:
Performance degradation if running many guests in z/VM.
Problem:
The parameter list that the kernel uses to enable the pfault mechanism must be double-word aligned. This is not necessarily the case since the data structure has a packed attribute annotation. If the alignment is incorrect a program check will be generated and the kernel will silently continue with the pfault feature disabled.
Solution:
Make sure data structure is properly aligned.
Problem-ID:
40293
Description:
Make sure data structure is properly aligned.
Symptom:
After adding an invalid LUN to zfcp, this LUN can not be removed again, the sysfs write for removal returns ENODEV.
Problem:
The unit_add calls internally scsi_add_device, this function calls the zfcp slave_destroy handler after determining that the unit does not exist. The zfcp slave_destroy handler waits for the scsi_add_device call to complete and we have a deadlock.
Solution:
Remove the wait in the zfcp slave_destroy handler. It was not required anyway and this resolves the deadlock.
Problem-ID:
40331
Description:
zfcp: Reduce flood on HBA trace.
Symptom:
The debug trace s390dbf/zfcp*hba contain "qual"-entries for all successfully processed FSF commands. Errors which would be of interest are hard to find or are already overwritten.
Problem:
The protocol to the adapter changed: A field that used to describe errors, now contains measurement data by default. This measurement data triggers the tracing of all normal responses.
Solution:
The fix is to simply remove the "qual" tracing: The responses with an interesting status are also traced as "ferr" or "perr" and all responses can be traced as "norm" with a higher trace level.
Problem-ID:
40333
Description:
zfcp: Remove SCSI devices when removing complete adapter
Symptom:
The sequence (1) chpid off, (2) wait for cio timeout, (3) chccwdev -d for a zfcp adapter leads to a hang in the cio kernel thread. After this scenario, cio is unusable.
Problem:
The above sequence calls the zfcp_ccw_remove callback which indicates that the CCW device for the FCP adapter disappeared. The callback in zfcp then tries to remove all data structures. Since the zfcp units are still registered with the SCSI stack, the removal waits for the SCSI devices to be removed, which does not happen.
Solution:
When removing all zfcp data structures, first remove the unit registrations with the SCSI stack.
Problem-ID:
38981

Everybody should apply this patch.

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

linux-2.6.16.tar.gz (from http://www.kernel.org/pub/linux/kernel/v2.6)
+ linux-2.6.16-s390-base-october2005.diff (IBM)
+ linux-2.6.16-s390-01-october2005.diff (IBM)
+ linux-2.6.16-s390-02-october2005.diff (IBM)
+ linux-2.6.16-s390-03-october2005.diff (IBM)
+ linux-2.6.16-s390-04-october2005.diff (IBM)
+ linux-2.6.16-s390-05-october2005.diff (IBM)
+ linux-2.6.16-s390-06-october2005.diff (IBM)
+ linux-2.6.16-s390-07-october2005.diff (IBM)
+ linux-2.6.16-s390-08-october2005.diff (IBM)
+ linux-2.6.16-s390-09-october2005.diff (IBM)
+ linux-2.6.16-s390-10-october2005.diff (IBM)
+ linux-2.6.16-s390-11-october2005.diff (IBM)
+ linux-2.6.16-s390-12-october2005.diff (IBM)
+ linux-2.6.16-s390-13-october2005.diff (IBM)
+ linux-2.6.16-s390-14-october2005.diff (IBM)
+ linux-2.6.16-s390-15-october2005.diff (IBM)
+ linux-2.6.16-s390-16-october2005.diff (IBM)
+ linux-2.6.16-s390-17-october2005.diff (IBM)
+ linux-2.6.16-s390-18-october2005.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.