Bug 872799 - net: WARN if struct ip_options was allocated directly by kmalloc [rhel-6.4]
net: WARN if struct ip_options was allocated directly by kmalloc [rhel-6.4]
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
Unspecified Unspecified
urgent Severity high
: rc
: ---
Assigned To: Jiri Pirko
Network QE
: ZStream
Depends On: 829109
Blocks: 877950
  Show dependency treegraph
Reported: 2012-11-03 05:46 EDT by Jiri Pirko
Modified: 2015-05-04 21:23 EDT (History)
8 users (show)

See Also:
Fixed In Version: kernel-2.6.32-339.el6
Doc Type: Bug Fix
Doc Text:
The INET socket interface has been modified to send a warning message when the ip_options structure is allocated directly by a third-party module using the kmalloc() function.
Story Points: ---
Clone Of: 872612
Last Closed: 2013-02-21 01:55:12 EST
Type: Bug
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 Jiri Pirko 2012-11-03 05:46:03 EDT
In case struct ip_options is allocated directly by kmalloc by a 3rd
party module, warn about this situation in get_ip_options_rcu().
Comment 2 RHEL Product and Program Management 2012-11-04 05:40:54 EST
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Comment 3 Jarod Wilson 2012-11-06 16:19:57 EST
Patch(es) available on kernel-2.6.32-339.el6
Comment 12 errata-xmlrpc 2013-02-21 01:55:12 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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