[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAE4R7bA9BqTF9UW95pfDujXo+jTfyDYcXfFCWthOJh_M0LQk4A@mail.gmail.com>
Date: Wed, 23 Sep 2015 21:59:17 -0700
From: Scott Feldman <sfeldma@...il.com>
To: Roopa Prabhu <roopa@...ulusnetworks.com>
Cc: "David S. Miller" <davem@...emloft.net>,
Netdev <netdev@...r.kernel.org>, Dept-GELinuxNICDev@...gic.com,
Jiří Pírko <jiri@...nulli.us>,
"stephen@...workplumber.org" <stephen@...workplumber.org>,
Jamal Hadi Salim <jhs@...atatu.com>,
Wilson Kok <wkok@...ulusnetworks.com>,
Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Subject: Re: [PATCH net-next] rtnl_fdb_dump: catch errors from ndo_fdb_dump
and ndo_dflt_fdb_dump
On Wed, Sep 23, 2015 at 9:21 AM, Roopa Prabhu <roopa@...ulusnetworks.com> wrote:
> From: Wilson Kok <wkok@...ulusnetworks.com>
>
> current ndo_fdb_dump and ndo_dflt_fdb_dump always return the current
> fdb index. They dont return errors. Which results in fdb dumps
> continuing on errors.
>
> In one such case where bridges and vxlan devices were involved,
> bridge driver returned -EMSGSIZE on a bridge, but since it continued
> on error, the next vxlan device fdb dump (which was smaller in size)
> succeeded, leaving fdb idx at an inconsistent value. This
> resulted in the bridge fdb entry getting skipped and vxlan
> fdb entry getting dumped twice.
>
> This patch changes ndo_fdb_dump() to return the status and pass the
> idx by reference for update. The dump aborts if non-zero status is
> returned.
>
> Signed-off-by: Wilson Kok <wkok@...ulusnetworks.com>
> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
Reviewed-by: Scott Feldman <sfeldma@...il.com>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists