From: Ian Campbell <ian.campbell@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>, Wei Liu <wei.liu2@citrix.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH net-next v2] xen-netback: implement dynamic multicast control
Date: Tue, 2 Feb 2016 11:53:45 +0000 [thread overview]
Message-ID: <1454414025.28781.146.camel@citrix.com> (raw)
In-Reply-To: <9d2b78b8dac54e6ea3f9889fd2a9db83@AMSPEX02CL03.citrite.net>
On Tue, 2016-02-02 at 11:48 +0000, Paul Durrant wrote:
> > -----Original Message-----
> > From: Wei Liu [mailto:wei.liu2@citrix.com]
> > Sent: 02 February 2016 11:47
> > To: Paul Durrant
> > Cc: netdev@vger.kernel.org; xen-devel@lists.xenproject.org; Ian
> > Campbell;
> > Wei Liu
> > Subject: Re: [PATCH net-next v2] xen-netback: implement dynamic
> > multicast
> > control
> >
> > On Tue, Feb 02, 2016 at 11:31:08AM +0000, Paul Durrant wrote:
> > [...]
> > > +static int xen_register_mcast_ctrl_watch(struct xenbus_device *dev,
> > > + struct xenvif *vif)
> > > +{
> > > + int err = 0;
> > > + char *node;
> > > + unsigned maxlen = strlen(dev->otherend) +
> > > + sizeof("/request-multicast-control");
> > > +
> > > + if (vif->mcast_ctrl_watch.node)
> > > + return -EADDRINUSE;
> > > +
> >
> > Sorry if I didn't make myself clear enough. I think EADDRINUSE should
> > also be logged.
> >
>
> Ok. Not sure how much noise that will cause though.
If this is a guest trigerable path then don't forget to use the
ratelimiting printk options....
Ian.
next prev parent reply other threads:[~2016-02-02 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 11:31 [PATCH net-next v2] xen-netback: implement dynamic multicast control Paul Durrant
2016-02-02 11:46 ` Wei Liu
2016-02-02 11:48 ` Paul Durrant
2016-02-02 11:53 ` Ian Campbell [this message]
2016-02-02 11:57 ` Paul Durrant
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=1454414025.28781.146.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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).