netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ying Xue <ying.xue@windriver.com>
To: <erik.hugne@ericsson.com>,
	<tipc-discussion@lists.sourceforge.net>, <jon.maloy@ericsson.com>,
	<maloy@donjonn.com>
Cc: <paul.gortmaker@windriver.com>, <richard.alpe@ericsson.com>,
	Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] tipc: fix regression bug where node events are not being generated
Date: Thu, 3 Apr 2014 14:37:18 +0800	[thread overview]
Message-ID: <533D019E.20608@windriver.com> (raw)
In-Reply-To: <1396506481-17362-1-git-send-email-erik.hugne@ericsson.com>

On 04/03/2014 02:28 PM, erik.hugne@ericsson.com wrote:
> From: Erik Hugne <erik.hugne@ericsson.com>
> 
> Commit 5902385a2440a55f005b266c93e0bb9398e5a62b ("tipc: obsolete
> the remote management feature")

I believe the commit is not merged into "net" tree yet, so currently the
regression problem _only_ exists in "net-next" tree. Therefore, it seems
unreasonable for us to deliver the patch to "net" tree now.

Regards,
Ying

 introduces a regression where node
> topology events are not being generated because the publication
> that triggers this: {0, <z.c.n>, <z.c.n>} is no longer available.
> This will break applications that rely on node events to discover
> when nodes join/leave a cluster.
> 
> We fix this by advertising the node publication when TIPC enters
> networking mode, and withdraws it upon shutdown.
> 
> Signed-off-by: Erik Hugne <erik.hugne@ericsson.com>
> Reviewed-by: Jon Maloy <jon.maloy@ericsson.com>
> Reviewed-by: Ying Xue <ying.xue@windriver.com>
> ---
> Patch is based on net-next, as the commit that introduces the
> regression, 5902385 was only recently applied to that tree.
> Sorry for the inconvenience.
> 
>  net/tipc/net.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/net/tipc/net.c b/net/tipc/net.c
> index 0374a81..4c564eb 100644
> --- a/net/tipc/net.c
> +++ b/net/tipc/net.c
> @@ -182,6 +182,8 @@ void tipc_net_start(u32 addr)
>  	tipc_bclink_init();
>  	write_unlock_bh(&tipc_net_lock);
>  
> +	tipc_nametbl_publish(TIPC_CFG_SRV, tipc_own_addr, tipc_own_addr,
> +			     TIPC_ZONE_SCOPE, 0, tipc_own_addr);
>  	pr_info("Started in network mode\n");
>  	pr_info("Own node address %s, network identity %u\n",
>  		tipc_addr_string_fill(addr_string, tipc_own_addr), tipc_net_id);
> @@ -192,6 +194,7 @@ void tipc_net_stop(void)
>  	if (!tipc_own_addr)
>  		return;
>  
> +	tipc_nametbl_withdraw(TIPC_CFG_SRV, tipc_own_addr, 0, tipc_own_addr);
>  	write_lock_bh(&tipc_net_lock);
>  	tipc_bearer_stop();
>  	tipc_bclink_stop();
> 

  reply	other threads:[~2014-04-03  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03  6:28 [PATCH] tipc: fix regression bug where node events are not being generated erik.hugne
2014-04-03  6:37 ` Ying Xue [this message]
2014-04-03 20:04 ` David Miller

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=533D019E.20608@windriver.com \
    --to=ying.xue@windriver.com \
    --cc=erik.hugne@ericsson.com \
    --cc=jon.maloy@ericsson.com \
    --cc=maloy@donjonn.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=richard.alpe@ericsson.com \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).