From: Ido Schimmel <idosch@idosch.org>
To: David Ahern <dsa@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, idosch@mellanox.com
Subject: Re: [PATCH net-next] net: dev: Fix non-RCU based lower dev walker
Date: Wed, 26 Oct 2016 23:46:43 +0300 [thread overview]
Message-ID: <20161026204643.cvtiasnsoj6ku7ex@splinter> (raw)
In-Reply-To: <1477513293-10117-1-git-send-email-dsa@cumulusnetworks.com>
On Wed, Oct 26, 2016 at 01:21:33PM -0700, David Ahern wrote:
> netdev_walk_all_lower_dev is not properly walking the lower device
> list. Commit 1a3f060c1a47 made netdev_walk_all_lower_dev similar
> to netdev_walk_all_upper_dev_rcu and netdev_walk_all_lower_dev_rcu
> but failed to update its netdev_next_lower_dev iterator. This patch
> fixes that.
>
> Fixes: 1a3f060c1a47 ("net: Introduce new api for walking upper and
> lower devices")
> Reported-by: Ido Schimmel <idosch@mellanox.com>
> Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
Tested-by: Ido Schimmel <idosch@mellanox.com>
Thanks David.
prev parent reply other threads:[~2016-10-26 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 20:21 [PATCH net-next] net: dev: Fix non-RCU based lower dev walker David Ahern
2016-10-26 20:46 ` Ido Schimmel [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=20161026204643.cvtiasnsoj6ku7ex@splinter \
--to=idosch@idosch.org \
--cc=dsa@cumulusnetworks.com \
--cc=idosch@mellanox.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).