[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AE1C82FB3D0EC64DB1F752C81CBD1101391D51E6@DFRE01.ent.ti.com>
Date: Tue, 28 Jun 2016 14:43:00 +0000
From: "Machani, Yaniv" <yanivma@...com>
To: Bob Copeland <me@...copeland.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Johannes Berg" <johannes@...solutions.net>,
"David S . Miller" <davem@...emloft.net>,
"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Hahn, Maital" <maitalm@...com>
Subject: RE: [PATCH 2/4] mac80211/cfg: mesh: fix healing time when a mesh
peer is disconnecting
On Tue, Jun 28, 2016 at 15:27:47, Bob Copeland wrote:
> linux- wireless@...r.kernel.org; netdev@...r.kernel.org; Hahn, Maital
> Subject: Re: [PATCH 2/4] mac80211/cfg: mesh: fix healing time when a
> mesh peer is disconnecting
>
> On Tue, Jun 28, 2016 at 02:13:05PM +0300, Yaniv Machani wrote:
> > From: Maital Hahn <maitalm@...com>
> >
> > Once receiving a CLOSE action frame from the disconnecting peer,
> > flush all entries in the path table which has this peer as the next hop.
>
> Please address the user-visible behavior in your commit messages.
> Does it crash? Does it send frames to an invalid peer? Do frames get dropped?
>
Hi Bob,
It was a crash, apparently already fixed by your patches some time ago.
I'll remove that part and resend the 2nd part (with some more 'why', and less typos..)
> > In addition, upon receiving a packet, if next hop is not found,
> > trigger PERQ immidiatly, instead of just putting it in the queue.
>
> "PREQ"
>
> Please split this into a separate patch that we can review separately
> (and also give the "why" in the commit log).
>
> > @@ -1011,6 +1011,7 @@ static void sta_apply_mesh_params(struct
> ieee80211_local *local,
> > if (sta->mesh->plink_state == NL80211_PLINK_ESTAB)
> > changed =
> mesh_plink_dec_estab_count(sdata);
> > sta->mesh->plink_state = params->plink_state;
> > + mesh_path_flush_by_nexthop(sta);
>
> This isn't necessary, caller should already be doing
> mesh_path_flush_by_nexthop() in every case I could see. Besides it
> cannot be done under plink lock.
>
I believe this was fixed in your patch "mac80211: mesh: flush paths outside of plink lock"
There is probably no need in that on the latest as well.
Thanks,
Yaniv
Powered by blists - more mailing lists