[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200320101630.13d80223@kicinski-fedora-PC1C0HJN>
Date: Fri, 20 Mar 2020 10:16:30 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Shannon Nelson <snelson@...sando.io>
Cc: netdev@...r.kernel.org, davem@...emloft.net
Subject: Re: [PATCH net-next 4/6] ionic: ignore eexist on rx filter add
On Thu, 19 Mar 2020 22:21:35 -0700 Shannon Nelson wrote:
> On 3/19/20 8:43 PM, Jakub Kicinski wrote:
> > On Thu, 19 Mar 2020 19:31:51 -0700 Shannon Nelson wrote:
> >> Don't worry if the rx filter add firmware request fails on
> >> EEXIST, at least we know the filter is there. Same for
> >> the delete request, at least we know it isn't there.
> >>
> >> Fixes: 2a654540be10 ("ionic: Add Rx filter and rx_mode ndo support")
> >> Signed-off-by: Shannon Nelson <snelson@...sando.io>
> > Why could the filter be there? Seems like the FW shouldn't have filters
> > the driver didn't add, could a flush/reset command help to start from
> > clean state?
> >
> > Just curious.
> Because there are use cases where the device is configured by an
> external centralized agent and may have already stuck the appropriate
> filters into the its list.
Thanks, seems a little leaky for the host to be able to probe the state
installed by the agent, but it does explain the need.
Powered by blists - more mailing lists