Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

Kernel patches

2005-04-28 kernel 2.4.21 bug fix patch 25 ("June 2003")

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-25-june2003.tar.gz / MD5 ... accumulated patch, recommended (2005-04-28)

linux-2.4.21-s390-25-june2003-patches.tar.gz / MD5 ... per-problem-patches, recommended (2005-04-28)

These patches contain the following linux kernel bug fixes:

Description:
lcs: System hang, when registering of multicast addresses fails.
Symptom:
Endless loop, when setting lcs device online and then registering of multicast addresses fails.
Problem:
Used list_for_each_entry() instead of list_for_each_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_safe().
Problem-ID:
14818
Description:
qeth: Layer2: VLAN unicast packets malformed.
Symptom:
Using qeth ethernet device in Layer 2 mode VLAN unicast packets will not arrive at vlan network device.
Problem:
The protocol is not set properly and VLAN tag is not correct either.
Solution:
First strip out the ethernet header and then set skb's protocol = encapsulated protocol.
Problem-ID:
15190
Description:
qeth: do not allow layer 2 mode in case of Hipersockets devices.
Symptom:
Hipersockets device initialization fails when layer 2 option is set.
Problem:
Using layer2 chandev option in conjunction with Hipersockets devices is not allowed but qeth tries to initialize Hipersockets devices in layer 2 mode as well.
Solution:
Turn off layer2 option in case of Hipersockets and go on with initializating Hipersockets in non-layer2 mode.
Problem-ID:
15194
Description:
s390dbf: Use more specific permissions for procfiles.
Symptom:
All s390dbf procfiles have same permissions.
Problem:
Permissions should be more specific. E.g read only views should have read permission, write only views should have write permission.
Solution:
Set correct permissions.
Problem-ID:
14372
Description:
scsi: LVM is unable to re-enable a path after a cable pull.
Symptom:
If FC cable is pulled for 10 minutes LVM is unable to re-enable the paths for all LUNs.
Problem:
After a timeout SCSI device is set offline which makes its recovery impossible.
Solution:
Introduce a new flag in SCSI host structure which, when set on, lets SCSI devices on this host never being set offline.
Problem-ID:
12614
Description:
z90crypt: Writing to /proc/driver/z90crypt can cause a kernel Oops.
Symptom:
Kernel Oops.
Problem:
Incorrect bounds checking on procfs write routine.
Solution:
Replace my string scanner with strstr and better error checking.
Problem-ID:
15058
Description:
zfcp: Increase retrying of exchange config data requests up to 2 minutes.
Symptom:
If exchange config data FSF request has being sent to FCP adapter while it is initializing a connection, exchange config data could not proceed even after retries.
Problem:
In case FSF request comes back with protocol status HOST_CONNECTION_INITIALIZING zfcp module makes 6 retries sleeping for 0.5 second between each retry.
Solution:
In case of HOST_CONNECTION_INITIALIZING let make a first retry in 1 second, then double the sleep time for each following retry until recovery exceeds 2 minutes.
Problem-ID:
15083

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)
+ linux-2.4.21-s390-05-june2003.diff (IBM)
+ linux-2.4.21-s390-06-june2003.diff (IBM)
+ linux-2.4.21-s390-07-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-08-june2003.diff (IBM)
+ linux-2.4.21-s390-09-june2003.diff (IBM)
+ linux-2.4.21-s390-10-june2003.diff (IBM)
+ xip2fs1 (see linuxvm.org/patches/index.html)
+ xip2fs2 (see linuxvm.org/patches/index.html)
+ linux-2.4.21-s390-11-june2003.diff (IBM)
+ linux-2.4.21-s390-12-june2003.diff (IBM)
+ linux-2.4.21-s390-13-june2003.diff (IBM)
+ linux-2.4.21-s390-14-june2003.diff (IBM)
+ linux-2.4.21-s390-15-june2003.diff (IBM)
+ linux-2.4.21-s390-16-june2003.diff (IBM)
+ linux-2.4.21-s390-17-june2003.diff (IBM)
+ linux-2.4.21-s390-18-fixed-june2003.diff (IBM)
+ linux-2.4.21-s390-19-june2003.diff (IBM)
+ linux-2.4.21-s390-20-june2003.diff (IBM)
+ linux-2.4.21-s390-21-june2003.diff (IBM)
+ linux-2.4.21-s390-22-june2003.diff (IBM)
+ linux-2.4.21-s390-23-june2003.diff (IBM)
+ linux-2.4.21-s390-24-june2003.diff (IBM)
+ linux-2.4.21-s390-25-june2003.diff (IBM)

Note: If On-demand timer is required, apply as last patch:
+ linux-2.4.21-s390-timer-04-june2003.diff (IBM)

Note: If you apply the above patches, you need as a minimum the 2005-02-14 version of the tape_3590 OCO module "tape3590-2.4.21-s390(x)-03-june2003.tar.gz".

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.