From: Andrew Jones <drjones@redhat.com>
To: "Jan Beulich" <JBeulich@suse.com>
Cc: "David Miller" <davem@davemloft.net>, <ian.campbell@citrix.com>,
<xen-devel@lists.xensource.com>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>,
liuw@liuw.name
Subject: Re: [Xen-devel] [PATCH] xen: netback: remove redundant xenvif_put
Date: Tue, 19 Feb 2013 09:58:03 +0100 [thread overview]
Message-ID: <20130219095803.17b28ec3@hawk.usersys.redhat.com> (raw)
In-Reply-To: <51233FF502000078000BF4AE@nat28.tlf.novell.com>
On Tue, 19 Feb 2013 08:03:49 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:
> >>> On 19.02.13 at 06:53, David Miller <davem@davemloft.net> wrote:
> > From: Andrew Jones <drjones@redhat.com>
> > Date: Mon, 18 Feb 2013 21:29:20 +0100
> >
> >> netbk_fatal_tx_err() calls xenvif_carrier_off(), which does
> >> a xenvif_put(). As callers of netbk_fatal_tx_err should only
> >> have one reference to the vif at this time, then the xenvif_put
> >> in netbk_fatal_tx_err is one too many.
> >>
> >> Signed-off-by: Andrew Jones <drjones@redhat.com>
> >
> > Applied.
>
> But this is wrong from all we can tell, we discussed this before
> (Wei pointed to the discussion in an earlier reply). The core of
> it is that the put here parallels the one in netbk_tx_err(), and
> the one in xenvif_carrier_off() matches the get from
> xenvif_connect() (which normally would be done on the path
> coming through xenvif_disconnect()).
I see the balance described by Ian in [1] now. Sorry that I missed
that previous discussion and generated this noise.
[1] http://marc.info/?l=xen-devel&m=136084174026977&w=2
drew
>
> And anyway - shouldn't changes to netback require an ack from
> Ian?
>
> Jan
>
next prev parent reply other threads:[~2013-02-19 8:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 20:29 [PATCH] xen: netback: remove redundant xenvif_put Andrew Jones
2013-02-18 20:58 ` Wei Liu
2013-02-19 5:53 ` David Miller
2013-02-19 8:03 ` [Xen-devel] " Jan Beulich
2013-02-19 8:58 ` Andrew Jones [this message]
2013-02-19 8:58 ` Ian Campbell
2013-02-19 18:06 ` David Miller
2013-02-20 9:23 ` Ian Campbell
2013-02-19 13:47 ` Ian Campbell
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=20130219095803.17b28ec3@hawk.usersys.redhat.com \
--to=drjones@redhat.com \
--cc=JBeulich@suse.com \
--cc=davem@davemloft.net \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuw@liuw.name \
--cc=netdev@vger.kernel.org \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).