[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170522.143846.1648727051789760165.davem@davemloft.net>
Date: Mon, 22 May 2017 14:38:46 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jarod@...hat.com
Cc: linux-kernel@...r.kernel.org, maheshb@...gle.com,
j.vosburgh@...il.com, vfalico@...il.com, andy@...yhouse.net,
netdev@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH net] bonding: fix randomly populated arp target array
From: Jarod Wilson <jarod@...hat.com>
Date: Fri, 19 May 2017 14:46:46 -0400
> In commit dc9c4d0fe023, the arp_target array moved from a static global
> to a local variable. By the nature of static globals, the array used to
> be initialized to all 0. At present, it's full of random data, which
> that gets interpreted as arp_target values, when none have actually been
> specified. Systems end up booting with spew along these lines:
...
> None of these were actually specified as ARP targets, and the driver does
> seem to clean up the mess okay, but it's rather noisy and confusing, leaks
> values to userspace, and the 255.255.255.255 spew shows up even when debug
> prints are disabled.
>
> The fix: just zero out arp_target at init time.
>
> While we're in here, init arp_all_targets_value in the right place.
>
> Fixes: dc9c4d0fe023 ("bonding: reduce scope of some global variables")
> CC: Mahesh Bandewar <maheshb@...gle.com>
> CC: Jay Vosburgh <j.vosburgh@...il.com>
> CC: Veaceslav Falico <vfalico@...il.com>
> CC: Andy Gospodarek <andy@...yhouse.net>
> CC: netdev@...r.kernel.org
> CC: stable@...r.kernel.org
> Signed-off-by: Jarod Wilson <jarod@...hat.com>
Whoops... applied, thanks Jarod.
Powered by blists - more mailing lists