lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 08 Jun 2010 14:55:26 -0600
From:	Tim Gardner <tim.gardner@...onical.com>
To:	netdev <netdev@...r.kernel.org>
Subject: 2.6.35-rc2, CONFIG_RPS is filling the dmesg log

With 2.6.35-rc2 my dmesg log is being flooded with messages like this:

br0 received packet on queue 4, but number of RX queues is 1

This machine is bridged for KVM and has 2 igb network adapters.

The root cause appears to be CONFIG_RPS=y and the fact that none of the 
drivers that call skb_record_rx_queue() perform their net device 
allocation using alloc_netdev_mq(), thereby initializing num_rx_queues 
to a maximum of 1.

Given that this is early RPS days, is the warning in get_rps_cpu() 
really necessary? It would appear that _all_ of the multi-receive queue 
devices that call skb_record_rx_queue() will cause this log noise.

By the way, how do you turn off CONFIG_RPS? The only way I could get it 
disabled was to change the default in net/Kconfig to 'n'.

rtg
-- 
Tim Gardner tim.gardner@...onical.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ