netdev - bonding inactive slaves vs rx

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130214.160657.1394358701071068786.davem@davemloft.net>
Date:	Thu, 14 Feb 2013 16:06:57 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	netdev@...r.kernel.org
CC:	eric.dumazet@...il.com, fubar@...ibm.com, andy@...yhouse.net
Subject: bonding inactive slaves vs rx_dropped

People are starting to notice that rx_dropped now increments on every
packet received on an bond's inactive slave.

I'm actually fine with rx_dropped incrementing in this situation.

The problem I want to address is that rx_dropped is encompassing
several unrelated situations and thus has become less useful for
diagnosis.

I think we should add some new RX stats such that we can get at
least a small amount of granularity for rx_dropped.

This way team, bond, etc. can increment a new netdev_stats->rx_foo in
this situation, and then someone doing diagnosis can see that
rx_dropped and rx_foo are incrementing at similar rates.
--
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