Bug 240752 - kernel dm io: panic on large request
kernel dm io: panic on large request
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
All Linux
high Severity high
: ---
: ---
Assigned To: Milan Broz
Martin Jenner
Depends On:
  Show dependency treegraph
Reported: 2007-05-21 09:39 EDT by Milan Broz
Modified: 2013-02-28 23:05 EST (History)
5 users (show)

See Also:
Fixed In Version: RHBA-2007-0791
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-15 11:27:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Milan Broz 2007-05-21 09:39:34 EDT
+++ This bug was initially created as a clone of Bug #240751 +++
RHEL 4.6. clone, reproducer script in bug 240751

Kernel will panic when creating ~6TB mirror because bio_alloc_bioset() will
return NULL if 'num_vecs' is too large.

Patch upstream
Comment 1 RHEL Product and Program Management 2007-05-21 10:06:50 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 4 Jason Baron 2007-07-03 18:50:52 EDT
committed in stream U6 build 55.16. A test kernel with this patch is available
from http://people.redhat.com/~jbaron/rhel4/
Comment 7 errata-xmlrpc 2007-11-15 11:27:26 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.