From: Mugunthan V N <mugunthanvnm@ti.com>
To: Richard Cochran <richardcochran@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: cpsw_ale clobbers learned addresses?
Date: Mon, 18 May 2015 14:42:17 +0530 [thread overview]
Message-ID: <5559ACF1.1080903@ti.com> (raw)
In-Reply-To: <20150513193816.GA11130@localhost.localdomain>
On Thursday 14 May 2015 01:08 AM, Richard Cochran wrote:
>
> It appears to me that cpsw_ale.c will possibly clobber addresses
> learned by the switch. When adding a new entry, the code reads the
> table until it finds an empty entry. Then, it writes the new value to
> that same index. However, nothing prevents the switch from using that
> same index between the read and the write.
>
> Or am I missing something?
>
There are chances that driver might overwrite address learnt by hardware
which was learnt between the instance getting free index and writing
table. Though the same software overwritten mac id will be updated on
the next packet received with same mac id.
Once driver updates the ALE table with valid entry hardware wont be
updating.
Regards
Mugunthan V N
prev parent reply other threads:[~2015-05-18 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 19:38 cpsw_ale clobbers learned addresses? Richard Cochran
2015-05-18 9:12 ` Mugunthan V N [this message]
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=5559ACF1.1080903@ti.com \
--to=mugunthanvnm@ti.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@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).