Skip to main content



Kernel 2.6 based: April 2004 stream

developerWorks

2005-04-05 kernel 2.6.5 bug fix patch 17 ("April 2004")

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.6.5-s390-17-april2004.tar.gz / MD5 ... accumulated patch, recommended (2005-04-05)

linux-2.6.5-s390-17-april2004-patches.tar.gz / MD5 ... per-problem-patches, recommended (2005-04-05)

These patches contain the following linux kernel bug fixes:

Description: cio: Remove debug code.
Symptom: None observable.
Problem: Superfluous code written for debugging a problem.
Solution: Remove the code.
Problem-ID: -

Description: ctcmpc: Enable further dynamic debug output.
Symptom: Debug information is not written.
Problem: More debug information should be written.
Solution: Change level of debug that can be obtained without a recompile of module and remove white spaces.
Problem-ID: -

Description: dcssblk: Fixed call for bio_io_error in case of I/O errors.
Symptom: System hangs, process accessing the block device stays in D state.
Problem: Incorrect length supplied on call of bio_io_error.
Solution: Call with full length of bio.
Problem-ID: 14821

Description: dcssblk: Disallow write requests to read only dcss block devices.
Symptom: Kernel oops when mounting, after explicit modification of the read-only attribute for the block device.
Problem: No verification of the data direction.
Solution: Add verification, issue a warning, and post I/O error on illegal requests.
Problem-ID: 14819

Description: kernel: 3270 error handling.
Symptom: The 3270 driver crashes if a control-c is sent while the device is in the online process.
Problem: Errors in the 3270 device startup sequence are not handled correctly.
Solution: Check for errors in the startup sequence and issue a halt_io if the startup sequence has been interrupted.
Problem-ID: 14817

Description: kernel: Any guest can send SMSG messages to cmm.
Symptom: SMSG messages sent by any guest can trigger cmm actions.
Problem: An arbitrary guest must not be allowed to trigger cmm actions. Only one specific guest (namely the one that serves a resource monitor) may send cmm messages.
Solution: Add a parameter that allows to specify the guest that may send SMSG messages to cmm.
Problem-ID: 14816

Description: kernel: diag10 on storage segments behind the first one.
Symptom: Addressing exception using cmm with more than one storage segment.
Problem: z/VM supports diag10 only for the first defined storage segment. If the collaborative memory management is used with a storage configuration with more than one segment this crashes the kernel.
Solution: Add a fixup section to the diag10 inline assembly to catch the addressing exception.
Problem-ID: 14815

Description: kernel: Static per-cpu variables and gcc 3.4.
Symptom: ipv6.ko needs unknown symbol per_cpu____icmppv6_socket.
Problem: gcc 3.4 removes statically defined per-cpu variables because all accesses to per-cpu variables are done by hidden relocations. gcc 3.4 and later compilers remove unused static variables.
Solution: Pass a reference to the inline assemblies that do the hidden relocations to make gcc aware of the fact that the static per-cpu variables are not unused.
Problem-ID: 14814

Description: lcs: System hang, when registering of multicast addresses fails.
Symptom: Endless loop, when registering of multicast addresses fails while setting lcs device online.
Problem: Used list_for_each_entry() instead of list_for_each_entry_safe() in a case where elements are removed from the list.
This is not allowed with list_for_each_entry.
Solution: Replace list_for_each_entry() with list_for_each_entry_safe().
Problem-ID: 14818

Description: qeth, claw: Several fixes for qeth and claw.
Symptom: Claw could not be loaded, DHCP with Layer 2 does not work properly.
Problem: Missing entry for channeltype claw in cu3088. Bug in Layer 2 qeth code.
Solution: Added entry for channeltype claw in cu3088. Fix Layer 2 code.
Problem-ID: -

Description: zfcp: Wrong handling of FSF states PORT_BOXED/LUN_BOXED.
Symptom: Recovery of ports and units after receiving unsolicited status "ACT updated" does not work.
Problem: FSF states PORT_BOXED/LUN_BOXED are not handled properly.
Solution: Handle FSF states PORT_BOXED/LUN_BOXED same as ACCESS_DENIED.
Problem-ID: -

Description: zfcp: Incorrect memset.
Symptom: Sg-list not correctly initialized.
Problem: Parameters for memset were interchanged.
Solution: Correct parameters for memset.
Problem-ID: -

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)

Back to top


Document options

Document options requiring JavaScript are not displayed


Contact the IBM team
If you want to contact the Linux on zSeries IBM team refer to the Contact the Linux on zSeries IBM team page