From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: Jonathan Toppins <jtoppins@cumulusnetworks.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
netdev@vger.kernel.org, Satish Ashok <sashok@cumulusnetworks.com>,
Andy Gospodarek <gospo@cumulusnetworks.com>
Subject: Re: [PATCH net-next v2 4/5] bonding: fix LACP PDU not sent on slave port sometimes
Date: Mon, 26 Jan 2015 16:45:38 -0800 [thread overview]
Message-ID: <21753.1422319538@famine> (raw)
In-Reply-To: <54C62D5E.9030200@cogentembedded.com>
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> wrote:
>Hello.
>
>On 1/26/2015 9:17 AM, Jonathan Toppins wrote:
>
>> From: Satish Ashok <sashok@cumulusnetworks.com>
>
>> When a slave is added to a bond and it is not in full duplex mode,
>> AD_PORT_LACP_ENABLED flag is cleared, due to this LACP PDU is not sent
>
> s/is not/not being/.
I don't have an issue with the original text, or the updating of
nearby debug messages to include the device name (below). Worst case
would be to respin and add a mention of this to the commit message.
-J
Signed-off-by: Jay Vosburgh <jay.vosburgh@canonical.com>
>> on slave. When the duplex is changed to full, the flag needs to be set
>> to send LACP PDU.
>
>> Cc: Andy Gospodarek <gospo@cumulusnetworks.com>
>> Reviewed-by: Nikolay Aleksandrov <nikolay@redhat.com>
>> Signed-off-by: Satish Ashok <sashok@cumulusnetworks.com>
>> Signed-off-by: Jonathan Toppins <jtoppins@cumulusnetworks.com>
>> ---
>> drivers/net/bonding/bond_3ad.c | 11 ++++++++---
>> 1 file changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/net/bonding/bond_3ad.c b/drivers/net/bonding/bond_3ad.c
>> index e3c96b2..cfc4a9c 100644
>> --- a/drivers/net/bonding/bond_3ad.c
>> +++ b/drivers/net/bonding/bond_3ad.c
>> @@ -2219,8 +2219,10 @@ static int bond_3ad_rx_indication(struct lacpdu *lacpdu, struct slave *slave,
>> switch (lacpdu->subtype) {
>> case AD_TYPE_LACPDU:
>> ret = RX_HANDLER_CONSUMED;
>> - netdev_dbg(slave->bond->dev, "Received LACPDU on port %d\n",
>> - port->actor_port_number);
>> + netdev_dbg(slave->bond->dev,
>> + "Received LACPDU on port %d slave %s\n",
>> + port->actor_port_number,
>> + slave->dev->name);
>> /* Protect against concurrent state machines */
>> spin_lock(&slave->bond->mode_lock);
>> ad_rx_machine(lacpdu, port);
>> @@ -2312,7 +2314,10 @@ void bond_3ad_adapter_duplex_changed(struct slave *slave)
>> port->actor_admin_port_key &= ~AD_DUPLEX_KEY_MASKS;
>> port->actor_oper_port_key = port->actor_admin_port_key |=
>> __get_duplex(port);
>> - netdev_dbg(slave->bond->dev, "Port %d changed duplex\n", port->actor_port_number);
>> + netdev_dbg(slave->bond->dev, "Port %d slave %s changed duplex\n",
>> + port->actor_port_number, slave->dev->name);
>
> The above 2 changes seem unrelated/undocumented in the change log...
>
>[...]
>
>WBR, Sergei
>
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2015-01-27 0:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 6:16 [PATCH net-next v2 0/5] bonding: various 802.3ad fixes Jonathan Toppins
2015-01-26 6:16 ` [PATCH net-next v2 1/5] bonding: update bond carrier state when min_links option changes Jonathan Toppins
2015-01-27 0:29 ` Jay Vosburgh
2015-01-26 6:16 ` [PATCH net-next v2 2/5] bonding: fix bond_open() don't always set slave active flag Jonathan Toppins
2015-01-27 0:33 ` Jay Vosburgh
2015-01-26 6:16 ` [PATCH net-next v2 3/5] bonding: fix incorrect lacp mux state when agg not active Jonathan Toppins
2015-01-27 2:42 ` Jay Vosburgh
2015-01-26 6:17 ` [PATCH net-next v2 4/5] bonding: fix LACP PDU not sent on slave port sometimes Jonathan Toppins
2015-01-26 12:04 ` Sergei Shtylyov
2015-01-27 0:45 ` Jay Vosburgh [this message]
2015-01-26 6:17 ` [PATCH net-next v2 5/5] bonding: cleanup and remove dead code Jonathan Toppins
2015-01-27 0:46 ` Jay Vosburgh
2015-01-27 0:49 ` [PATCH net-next v2 0/5] bonding: various 802.3ad fixes Andy Gospodarek
2015-01-28 1:09 ` 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=21753.1422319538@famine \
--to=jay.vosburgh@canonical.com \
--cc=andy@greyhouse.net \
--cc=gospo@cumulusnetworks.com \
--cc=jtoppins@cumulusnetworks.com \
--cc=netdev@vger.kernel.org \
--cc=sashok@cumulusnetworks.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=vfalico@gmail.com \
/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).