Red Hat ENTERPRISE 5.4 RELEASE NOTES, Manual

Page: 154 / 466

Chapter 1. Package Updates
136
• All
vports
are now alerted of any asynchronous events.
• A bug that caused kernel panics with the QLogic 2472 card is now fixed.
• The
stop_firmware
command is no longer retried if the first attempt results in a times out.
• The sector mask value is no longer based on the fixed
optrom
size.
• A bug that caused frequent path failures during I/O on multipathed devices is now fixed.
(
BZ#244967
1011
)
• The driver source code is now kABI-compliant.
•
dcbx
pointers are now set to
NULL
after freeing memory.
• The
qla4xxx
driver now features improved driver fault recovery. This update fixes a bug in the
driver that prevented adapter recovery if there were outstanding commands detected on the host
adapter. (
BZ#497478
1012
)
1.110.9.11. Miscellaneous Updates
• This update removes the
kfree
function from
kret_probelock
's scope so as to avoid a
deadlock that could occur if
kretprobe_flush_task()
probes the
kfree
function while holding
kretprobe_lock
spinlock. In addition, the
kprobe
functionality has been disallowed on the
atomic_notifier_call_chain
function to avoid numerous recursive faults occurring when it is
called by
kprobe
after a re-entry. (
BZ#210555
1013
)
• PCI devices would disappear in Xen Paravirtual guest system upon reboot or reset. This was
identified as a problem with information about PCI devices being removed from
xenstore
before
xend
was able to create a configuration for the rebooted domain. Code has been amended in
xenbus.c
to correct this behavior. (
BZ#233801
1014
)
• A kernel crash occurred when a Xen user specified the
mem=
(or
highmem=
) command via the
command line on either the host or guest systems. This was caused by the array allocated to the
p2m
table being too small which resulted in a page fault during the subsequent
memcpy()
. This
update decreases the memory reservation and only copies the appropriate number of entries into
the
p2m
table.(
BZ#240429
1015
)
• RAID 0, RAID 1, RAID 10 and RAID 5 configurations have previously set
q->merge_bvec_fn
(a
function that asks a device driver if the next vector entry will fit into a bio constructed by a process)
in a way that rejects bios crossing its stripe. A device mapper will accept a bio that has two or
more vector entries and a size equal to or less than a page that crosses a stripe boundary, but the
underlying RAID device will not.
This update configures the device mapper to set a one-page maximum request size and set its own
q->merge_bvec_fn
to reject any bios with multiple vector entries that span more pages. This fix
precludes the generation of bios that will be rejected by a
q->merge_bvec_fn
controlled by RAID
0, 1, 10 or 5.
BZ#223947
1016
)
• This update includes numerous patches to enable Gigabyte pagetable support. (
BZ#251982
1017
).
•
0002-hugetlb-multiple-hstates-for-multiple-page-sizes.patch
•
0003-hugetlbfs-per-mount-huge-page-sizes.patch