From: Nikolay Aleksandrov <nikolay@redhat.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, andy@greyhouse.net
Subject: Re: [PATCH net 2/3] bonding: Fix initialize after use for 3ad machine state spinlock
Date: Mon, 18 Feb 2013 22:51:20 +0100 [thread overview]
Message-ID: <5122A258.9000707@redhat.com> (raw)
In-Reply-To: <21258.1361223190@death.nxdomain>
On 18/02/13 22:33, Jay Vosburgh wrote:
> Nikolay Aleksandrov <nikolay@redhat.com> wrote:
>
>> The 3ad machine state spinlock can be used before it is inititialized
>> while doing bond_enslave() (and the port is being initialized) since
>> port->slave is set before the lock is prepared, thus causing soft
>> lock-ups and a multitude of other nasty bugs.
>
> Does this change cause the "uninitialized port" warnings in
> bond_3ad_state_machine_handler and bond_3ad_rx_indication to
> intermittently print during the enslavement process? If so (and it
> looks to me like it will), I think the warnings should be removed, since
> after this change, port->slave being NULL isn't really an error
> condition that needs a warning to the log.
>
This change couldn't cause that, it only initializes the spin lock
before the slave is set, currently after the first patch of this series
this is no longer a requirement as far as I can tell the only code that
can access the lock before the slave is set was that one, but it still
is a bug that can manifest later. I don't think it has anything to do
with the warnings, the only change is that the spin lock is initialized
prior to setting the slave to the port.
Am I missing something here ?
>> Signed-off-by: Nikolay Aleksandrov <nikolay@redhat.com>
>> ---
>> drivers/net/bonding/bond_3ad.c | 9 ++++-----
>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/net/bonding/bond_3ad.c b/drivers/net/bonding/bond_3ad.c
>> index 1720742..96d471e 100644
>> --- a/drivers/net/bonding/bond_3ad.c
>> +++ b/drivers/net/bonding/bond_3ad.c
>> @@ -389,13 +389,13 @@ static u8 __get_duplex(struct port *port)
>>
>> /**
>> * __initialize_port_locks - initialize a port's STATE machine spinlock
>> - * @port: the port we're looking at
>> + * @port: the slave of the port we're looking at
>> *
>> */
>> -static inline void __initialize_port_locks(struct port *port)
>> +static inline void __initialize_port_locks(struct slave *port)
>> {
>> // make sure it isn't called twice
>> - spin_lock_init(&(SLAVE_AD_INFO(port->slave).state_machine_lock));
>> + spin_lock_init(&(SLAVE_AD_INFO(port).state_machine_lock));
>
> Change the name of the variable here, too, not just the type.
> This is confusing.
>
> -J
Thanks, I saw that after posting, I have prepared this change already.
>
>> }
>>
>> //conversions
>> @@ -1910,6 +1910,7 @@ int bond_3ad_bind_slave(struct slave *slave)
>>
>> ad_initialize_port(port, bond->params.lacp_fast);
>>
>> + __initialize_port_locks(slave);
>> port->slave = slave;
>> port->actor_port_number = SLAVE_AD_INFO(slave).id;
>> // key is determined according to the link speed, duplex and user key(which is yet not supported)
>> @@ -1932,8 +1933,6 @@ int bond_3ad_bind_slave(struct slave *slave)
>> port->next_port_in_aggregator = NULL;
>>
>> __disable_port(port);
>> - __initialize_port_locks(port);
>> -
>>
>> // aggregator initialization
>> aggregator = &(SLAVE_AD_INFO(slave).aggregator);
>> --
>> 1.7.11.7
>>
>
> ---
> -Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
>
next prev parent reply other threads:[~2013-02-18 21:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 17:59 [PATCH net 1/3] bonding: Fix race condition between bond_enslave() and bond_3ad_update_lacp_rate() Nikolay Aleksandrov
2013-02-18 17:59 ` [PATCH net 2/3] bonding: Fix initialize after use for 3ad machine state spinlock Nikolay Aleksandrov
2013-02-18 21:33 ` Jay Vosburgh
2013-02-18 21:51 ` Nikolay Aleksandrov [this message]
2013-02-19 5:52 ` David Miller
2013-02-18 17:59 ` [PATCH net-next 3/3] bonding: fix bond_release_all inconsistencies Nikolay Aleksandrov
2013-02-18 21:56 ` Jay Vosburgh
2013-02-18 22:13 ` Nikolay Aleksandrov
2013-02-18 23:17 ` Jay Vosburgh
2013-02-18 21:09 ` [PATCH net 1/3] bonding: Fix race condition between bond_enslave() and bond_3ad_update_lacp_rate() Jay Vosburgh
2013-02-19 5:52 ` David Miller
2013-02-19 0:09 ` [PATCH net-next v2 3/3] bonding: fix bond_release_all inconsistencies Nikolay Aleksandrov
2013-02-19 3:12 ` Jay Vosburgh
2013-02-19 5:53 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5122A258.9000707@redhat.com \
--to=nikolay@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=fubar@us.ibm.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).