Bug 461442 - VLAN driver logs excessive messages in kernel message log (dmesg)
Summary: VLAN driver logs excessive messages in kernel message log (dmesg)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Danny Feng
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-08 02:49 UTC by starlight
Modified: 2010-03-30 07:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 07:30:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
posted patch (1.90 KB, patch)
2009-09-28 10:14 UTC, Danny Feng
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0178 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.5 kernel security and bug fix update 2010-03-29 12:18:21 UTC

Description starlight 2008-09-08 02:49:15 UTC
Description of problem:

If one subscribes to a few hundred multicasts on one or more
VLAN interfaces, the VLAN driver logs an excessive number of
messages and wipes out the more useful information in the
kernel message log that is viewed with the 'dmesg' command.

example:

vlan2003: add 01:00:5e:00:05:e4 mcast address to master interface
vlan2003: del 01:00:5e:77:a0:10 mcast address from master interface
.
.
.
ad nauseam

Version-Release number of selected component (if applicable):

kernel 2.6.18-92.1.10.el5

How reproducible:

Configure an 801.1q trunked VLAN or two with the
'vconfig' command.  Then subscribe to a hundred
or more multicasts on them.
  
Actual results:

Excessive number of messages that completely wipe out
the kernel message log.

Expected results:

No messages should be logged.

Additional info:

Don't need to know about these events.  One
can always look at '/proc/net/dev_mcast' to see the
multicast subscriptions.  It should take about five
minutes to remove the message or make it a debug-only
logging event.

Comment 1 Danny Feng 2009-08-19 03:16:15 UTC
those messages was printk with KERN_DEBUG, the lowest level (8) of log messages, that's for debug only. You can use "dmesg -n 7" to filter out all debug messages...

Comment 3 Danny Feng 2009-09-28 10:14:34 UTC
Created attachment 362877 [details]
posted patch

Comment 5 Don Zickus 2009-11-17 21:55:33 UTC
in kernel-2.6.18-174.el5
You can download this test kernel from http://people.redhat.com/dzickus/el5

Please do NOT transition this bugzilla state to VERIFIED until our QE team
has sent specific instructions indicating when to do so.  However feel free
to provide a comment indicating that this fix has been verified.

Comment 8 errata-xmlrpc 2010-03-30 07:30:20 UTC
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 therefore 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.

http://rhn.redhat.com/errata/RHSA-2010-0178.html


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