From: Jay Vosburgh <fubar@us.ibm.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: Andy Gospodarek <andy@greyhouse.net>,
"David S. Miller" <davem@davemloft.net>,
Veaceslav Falico <vfalico@redhat.com>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net 0/3] bonding: add port protection for bond_3ad_xxx_change()
Date: Fri, 13 Dec 2013 14:26:02 -0800 [thread overview]
Message-ID: <28416.1386973562@death.nxdomain> (raw)
In-Reply-To: <52AAD36B.40103@huawei.com>
Ding Tianhong <dingtianhong@huawei.com> wrote:
>Jay Vosburgh said that the bond_3ad_adapter_speed_changed and
>bond_3ad_adapter_duplex_changed is called with RTNL only, and
>the functions will modify the port's information with no further
>locking, they will not mutex against bond state machine and
>incoming LACPDU which do not hold RTNL, So I add port lock to
>protect the port information.
>
>But they are not critical bugs, they exist since day one, and till
>now they have never been hit and reported, because change for speed
>and duplex is very rare, and will not occur critical problem.
>
>The comments in the function is very old, cleanup the comments together.
For entire series:
Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
-J
>Ding Tianhong (3):
> bonding: protect port for bond_3ad_adapter_speed_changed()
> bonding: protect port for bond_3ad_adapter_duplex_changed()
> bonding: protect port for bond_3ad_handle_link_change()
>
> drivers/net/bonding/bond_3ad.c | 45 +++++++++++++++++++++++++++++++-----------
> 1 file changed, 33 insertions(+), 12 deletions(-)
>
>--
>1.8.0
---
-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com
next prev parent reply other threads:[~2013-12-13 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 9:29 [PATCH net 0/3] bonding: add port protection for bond_3ad_xxx_change() Ding Tianhong
2013-12-13 22:26 ` Jay Vosburgh [this message]
2013-12-18 21: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=28416.1386973562@death.nxdomain \
--to=fubar@us.ibm.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.