2006-11-02 kernel 2.6.5 bug fix patch 40 ("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-40-april2004.tar.gz / MD5 ... accumulated patch, recommended (2006-11-02)

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

These patches contain the following linux kernel bug fixes:

Description:
cio: 0 is a valid CHPID.
Symptom:
/sys/devices/css0/chp0.0 is not created, although devices that use the channel path with id 0 are present in the system.
Problem:
0 was not considered a valid CHPID.
Solution:
Check for CHPID validity via the path installed mask (pim).
Problem-ID:
27654
Description:
cio: I/O request failure after CHPID deactivation.
Symptom:
CCW device I/O fails after CHPID vary off operation despite remaining paths.
Problem:
After I/O finishes during CHPID vary grace period, path verification is not started.
Solution:
Start path verification after I/O finished during grace period.
Problem-ID:
28548
Description:
cio: css_probe_device() must be called enabled.
Symptom:
'BUG: sleeping function called from invalid context' message when re-defining a device number with 'DEFINE xxxx AS yyyy' in z/VM.
Problem:
In case of a revalidate machine check, css_probe_device() was called while interrupts were still disabled.
Solution:
Move call to css_probe_device() after interrupts have been re-enabled.
Problem-ID:
28522
Description:
cio: inaccessible device after CHPID deactivation.
Symptom:
CCW device enters state 'no device' after a CHPID is deactivated.
Problem:
Internal I/O operations are not re-tried when aborted by CHPID deactivation.
Solution:
Re-try internal I/O when aborted by CHPID deactivation.
Problem-ID:
28547
Description:
cio: incorrect detection of unsolicited interrupts during sense pgid.
Symptom:
Calls to set a device online with path grouping may get stuck in some cases. This can result in a hang during boot or when trying to set a device online at a later time.
Problem:
Certain device conditions were discarded in response to unsolicited interrupts.
Solution:
Check subchannel activity in these cases and re-try if the subchannel is idle.
Problem-ID:
26648
Description:
cio: incorrect device operational notification.
Symptom:
DASD device driver reports failed I/O request after running out of re-tries when channel paths become unavailable during path verification.
Problem:
Device operational notifications are reported to the device driver even though device has become unavailable during the course of path verification.
Solution:
Reset device operational notification flag on failed path verification.
Problem-ID:
28177
Description:
cio: incorrect no-path indication after machine check.
Symptom:
Device enters no-path state after disabling a channel path via the SE even though another path has been reenabled at the SE.
Problem:
Device is set into no-path state before triggering path verification even though other paths may have become available.
Solution:
Trigger path verification before setting a device into no-path state.
Problem-ID:
27255
Description:
cio: path group not updated by CHPID vary operation.
Symptom:
CHPIDs that are logically varied off will not be removed from a CCW device's path group.
Problem:
Command resign-from-pathgroup is issued with invalid path mask of 0 because internal CCW operations are masked by the logical path mask after the relevant bits are cleared by the vary operation.
Solution:
Do not apply logical path mask to internal operations.
Problem-ID:
27257
Description:
cio: path verification ignores re-appearing channel paths.
Symptom:
Re-appearing channel paths are sometimes not utilized by CCW devices.
Problem:
Path verification incorrectly relies on path-operational-mask information which is not updated until a channel path has been used again.
Solution:
Modify path verification procedure to always query all available paths to a device.
Problem-ID:
27258
Description:
cio: race condition leaves device in inaccessible state.
Symptom:
Availability of CCW device becomes 'no path' or 'no device' for no apparent reason.
Problem:
Asynchronous subchannel evaluation operates channel without proper locking.
Solution:
Add locking to subchannel evaluation.
Problem-ID:
27256
Description:
cio: subchannel scan loop for re-appearing channel paths ends early.
Symptom:
Subchannel may incorrectly remain in state no-path after channel paths have re-appeared.
Problem:
The scan for subchannels which are using a channel path ends at the first occurrence if a full link address was provided by the channel subsystem.
Solution:
Always continue scan for subchannels after first occurrence.
Problem-ID:
27254
Description:
dasd: Failing partition detection during device bring-up.
Symptom:
Setting a device online either failing or leading to invalid (-24) partition size.
Problem:
DASD allows to open a device as soon as gendisk is registered, which means that the device is a fake device (capacity=0) and we do know nothing about blocksize and partitions at that point of time.
In case the device is opened by someone, the bdev and inode creation is done with the fake device info and the following partition detection code is just using these wrong data (capacity = 0 minus offset 24 leading to a partition size = -24).
Solution:
Modify the DASD state machine to make sure that the open is rejected until the device analysis is either finished or a unformatted device was detected.
Problem-ID:
21059
Description:
kernel: incorrect copy_in_user.
Symptom:
Incorrect execution of 31-bit programs on a 64-bit kernel.
Problem:
The copy_in_user function copies 1 byte too much.
Solution:
Correct the copy_in_user function.
Problem-ID:
26754
Note:
applicable for 64-bit Linux, only
Description:
kernel: user readable un-initialized kernel memory.
Symptom:
None.
Problem:
A user space program can read un-initialized kernel memory by appending to a file from a bad address and then reading the result back. The cause is the copy_from_user function that does not clear the remaining bytes of the kernel buffer after it got a fault on the user space address.
Solution:
Fix the copy_from_user function to clear the remaining bytes of the kernel buffer after a user space fault.
Problem-ID:
27706
Description:
qeth: After cable pull (out/in) device does not work.
Symptom:
After cable pulling, DMESG said that qeth successfully recovered, but PING ist not working.
Problem:
Recovery procedure does not correctly handle netif carrier.
Solution:
When the link is established again call netif_carrier_on before starting the card recovery.
Problem-ID:
26756
Description:
qeth: do not manipulate outgoing cloned skbs.
Symptom:
tcpdump shows damaged LL headers for outgoing vlan packets.
Problem:
The skb given to qeth is a clone, so qeth is not allowed to change the skb.
Solution:
Create a copy of the skb and change the copy not the clone.
Problem-ID:
28120
Description:
qeth: VLAN header re-ordering does not work on packets received through qeth interface in layer 2 mode.
Symptom:
dhcpcd (dhcp client) does not work.
Problem:
qeth removes vlan tag and uses vlan_hwaccel_rx(). vlan driver does not do header re-ordering because it is not necessary for hw accelerated packets. Looking at the packet in memory the ip header is prefixed by vlan (not ethernet as expected by dhcpcd).
Solution:
Since qeth layer 2 mode is not hardware accelerated, qeth should not remove vlan tag and call vlan_hwaccel_rx(). Leave the packet as is and call netif_rx() instead of vlan_hwaccel_rx(), so that the vlan driver will do the job of header re-ordering.
Problem-ID:
27068
Description:
z90crypt: Logfile flooding when no crypto hardware is available.
Symptom:
z90crypt floods logfiles when no hardware is available with unnecessary error messages.
Problem:
probe_crypto_domain() in z90main.c is periodically called to scan AP bus for devices. If no devices are found an error message is printed regardless if this error message was printed earlier.
Solution:
Provide new PRINTK.*_ONCE macro to print an error message only once.
Problem-ID:
25692

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)
+ linux-2.6.5-s390-32-april2004.diff (IBM)
+ linux-2.6.5-s390-33-april2004.diff (IBM)
+ linux-2.6.5-s390-34-april2004.diff (IBM)
+ linux-2.6.5-s390-35-april2004.diff (IBM)
+ linux-2.6.5-s390-36-april2004.diff (IBM)
+ linux-2.6.5-s390-37-april2004.diff (IBM)
+ linux-2.6.5-s390-38-april2004.diff (IBM)
+ linux-2.6.5-s390-39-april2004.diff (IBM)
+ linux-2.6.5-s390-40-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.