Kernel 2.4 based: June 2003 stream

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-13-june2003.tar.gz / MD5 ... accumulated patch, recommended (2004-05-18)

linux-2.4.21-s390-13-june2003-patches.tar.gz / MD5 ... per-problem-patches, recommended (2004-05-18)

These patches contain the following linux kernel bug fixes:

Description:

iucv: restart of multiple IUCV connections fails.

Symptom:

Further IUCV connections are only possible after reloading of module netiucv.

Problem:

When restarting IUCV connections, the old IUCV pathids are not reused. Thus repeated restart of a single IUCV connection resp. few restarts of multiple IUCV connections result in reaching the maximum number limit of IUCV paths.

Solution:

Handling of an IUCV connection severed by partner is changed: No reconnect is made; instead the IUCV connection stays in state STARTWAIT till a "Connection Pending" interrupt arrives.

Problem-ID:

7640

Description:

kernel: mlock() gets stuck in get_user_pages/follow_page.

Symptom:

Process doing mlock loops in the kernel with kernel locks held.

Problem:

set_pte/pte_mkdirty does not cause pte_dirty to return true, but the common mm code relies on it.

Solution:

Set page dirty if required but don't loop on !pte_dirty().

Problem-ID:

8210

Description:

qeth: module use count problem in performance statistics.

Symptom:

Negative qeth module use count.

Problem:

Forgot to increase module counter when reading perf stats.

Solution:

Call MOD_INC_USE_COUNT appropriately.

Problem-ID:

8394

Description:

zfcp: zfcp logs a wrong message when trying to register a LUN which is already in use.

Symptom:

If a LUN is already in use by another guest zfcp module says that there is no access to a LUN.

Problem:

zfcp modules analyzes FSF status qualifier in a false order.

Solution:

Let zfcp module analyze FSF status qualifier correctly.

Problem-ID:

7036

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)

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

Back to top