All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Copeland <me@bobcopeland.com>
To: Henning Rogge <hrogge@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	"David S. Miller" <davem@davemloft.net>,
	Henning Rogge <henning.rogge@fkie.fraunhofer.de>
Subject: Re: [PATCH 2/2] mac80211: let unused MPP table entries timeout
Date: Tue, 26 Jan 2016 18:17:59 -0500	[thread overview]
Message-ID: <20160126231759.GA9708@localhost> (raw)
In-Reply-To: <1453190672-9748-3-git-send-email-henning.rogge@fkie.fraunhofer.de>

On Tue, Jan 19, 2016 at 09:04:32AM +0100, Henning Rogge wrote:
>  	err = -ENXIO;
> -enddel:
> +enddelpath:

Concur about it being better to leave this label alone, also the diff looks
weird because it continues:

> +	mesh_paths_generation++;
> +	spin_unlock(&tbl->hashwlock[hash_idx]);
> +	read_unlock_bh(&pathtbl_resize_lock);
> +	return err;
> +}

[...]

> +	err = -ENXIO;
> +enddelmpp:
>  	mesh_paths_generation++;
>  	spin_unlock(&tbl->hashwlock[hash_idx]);
>  	read_unlock_bh(&pathtbl_resize_lock);

At first I wondered why the last half of the function was changed, but then
I saw that.  Shouldn't the above be "mpp_paths_generation++;"?

In general I'd like to merge these two into one function; the only thing
different is the initial table pointer that gets dereferenced and the
generation counter (and now the labels).  So something like this should
be doable:

static int mesh_table_delete(struct ieee80211_sub_if_data *sdata,
                             struct mesh_table *tbl,
                             const u8 *addr)
{
        /* basically what mesh_path_del is today */
}

int mesh_path_del(...)
{
        tbl = resize_dereference_mesh_paths();
        ret = mesh_table_delete(sdata, tbl, addr);
        mesh_paths_generation++;
        return ret;
}

int mpp_path_del(...)
{
        tbl = resize_dereference_mpp_paths();
        ret = mesh_table_delete(sdata, tbl, addr);
        mpp_paths_generation++;
        return ret;
}

-- 
Bob Copeland %% http://bobcopeland.com/

  parent reply	other threads:[~2016-01-26 23:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  8:04 [PATCH 0/2] mac80211: add cleanup path for MPP table entries Henning Rogge
2016-01-19  8:04 ` [PATCH 1/2] mac80211: Remove connected MPP table entries with MPath Henning Rogge
2016-01-26 11:41   ` Johannes Berg
2016-01-26 18:36     ` Bob Copeland
2016-01-26 19:04       ` Henning Rogge
2016-01-26 20:53       ` Johannes Berg
2016-01-26 21:22         ` Bob Copeland
2016-01-26 21:31           ` Johannes Berg
2016-01-26 21:32             ` Johannes Berg
2016-01-26 21:44               ` Bob Copeland
2016-01-19  8:04 ` [PATCH 2/2] mac80211: let unused MPP table entries timeout Henning Rogge
2016-01-22 20:30   ` Bob Copeland
2016-01-23  9:39     ` Henning Rogge
2016-01-23 15:15       ` Bob Copeland
2016-01-24 17:53         ` Henning Rogge
2016-01-26 11:44   ` Johannes Berg
2016-01-26 19:54     ` Henning Rogge
2016-01-26 23:17   ` Bob Copeland [this message]
2016-01-28 13:44 ` [PATCH 0/2] mac80211: add cleanup path for MPP table entries Bob Copeland
2016-01-28 15:07   ` Henning Rogge
2016-01-28 15:12     ` Bob Copeland

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=20160126231759.GA9708@localhost \
    --to=me@bobcopeland.com \
    --cc=davem@davemloft.net \
    --cc=henning.rogge@fkie.fraunhofer.de \
    --cc=hrogge@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.