Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: YanBo <dreamfly281@gmail.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>,
	Javier Cardona <javier@cozybit.com>,
	Luis Carlos Cobo <luisca@cozybit.com>
Subject: Re: [RFC V2] mac80211: mesh portal functionality support
Date: Sun, 21 Sep 2008 14:11:11 +0200	[thread overview]
Message-ID: <1221999071.3023.21.camel@johannes.berg> (raw)
In-Reply-To: <1197ff4c0809210450u556538actc6f37390d3079fbc@mail.gmail.com> (sfid-20080921_135057_878688_51244EC5)

[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]

On Sun, 2008-09-21 at 19:50 +0800, YanBo wrote:

> @@ -226,6 +227,8 @@ int mesh_nexthop_lookup(struct sk_buff *skb,
>  void mesh_path_start_discovery(struct ieee80211_sub_if_data *sdata);
>  struct mesh_path *mesh_path_lookup(u8 *dst,
>  		struct ieee80211_sub_if_data *sdata);
> +struct mesh_path *mpp_path_lookup(u8 *dst, struct
> ieee80211_sub_if_data *sdata);

there's a line-wrap here for some reason


>  static struct mesh_table *mesh_paths;
> +static struct mesh_table *mpp_paths; /* Store pathes for MPP&MAP */

Can you add a note why we need a separate hash table at all?

> @@ -475,11 +589,19 @@ static int mesh_path_node_copy(struct hlist_node
> *p, struct mesh_table *newtbl)
>  int mesh_pathtbl_init(void)
>  {
>  	mesh_paths = mesh_table_alloc(INIT_PATHS_SIZE_ORDER);
> +	if (!mesh_paths)
> +		return -ENOMEM;
>  	mesh_paths->free_node = &mesh_path_node_free;
>  	mesh_paths->copy_node = &mesh_path_node_copy;
>  	mesh_paths->mean_chain_len = MEAN_CHAIN_LEN;
> -	if (!mesh_paths)
> -		return -ENOMEM;
> +
> +	mpp_paths = mesh_table_alloc(INIT_PATHS_SIZE_ORDER);
> +	if (!mpp_paths)
> + 		return -ENOMEM;

This leaks 'mesh_paths'.

> +	if (mesh_hdr->flags == 2){

that should use the constant you introduced

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2008-09-21 12:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17  9:00 [RFC] mac80211: mesh portal functionality support YanBo
2008-09-21 11:50 ` [RFC V2] " YanBo
2008-09-21 12:11   ` Johannes Berg [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=1221999071.3023.21.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=dreamfly281@gmail.com \
    --cc=javier@cozybit.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=luisca@cozybit.com \
    /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