From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: David Vrabel <david.vrabel@citrix.com>,
xen-devel@lists.xen.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH 3/5] xen-pcifront: handle backend CLOSED without CLOSING
Date: Fri, 30 Nov 2012 17:39:39 -0500 [thread overview]
Message-ID: <20121130223939.GA7749@phenom.dumpdata.com> (raw)
In-Reply-To: <CAErSpo7Vob9CiRxK+E2nV2V7G4FCss6zLCPO93PMSDj9G55ywg@mail.gmail.com>
On Fri, Nov 30, 2012 at 02:42:14PM -0700, Bjorn Helgaas wrote:
> On Fri, Nov 30, 2012 at 11:41 AM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> > On Fri, Oct 19, 2012 at 6:59 AM, Konrad Rzeszutek Wilk
> > <konrad.wilk@oracle.com> wrote:
> >> On Thu, Oct 18, 2012 at 11:03:36AM +0100, David Vrabel wrote:
> >>> From: David Vrabel <david.vrabel@citrix.com>
> >>>
> >>> Backend drivers shouldn't transistion to CLOSED unless the frontend is
> >>> CLOSED. If a backend does transition to CLOSED too soon then the
> >>> frontend may not see the CLOSING state and will not properly shutdown.
> >>>
> >>> So, treat an unexpected backend CLOSED state the same as CLOSING.
> >>>
> >>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> >>> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> >>> ---
> >>> Cc: linux-pci@vger.kernel.org
> >>> Cc: Bjorn Helgaas <bhelgaas@google.com>
> >>
> >> Bjorn, do you want me to prep a git pull with this patch
> >> or can I have your Ack to put it my tree and have it part of my
> >> git pull to Linus?
> >
> > Sorry, I missed this. I can put it in my -next branch for the v3.8
> > merge window. Would that work for you?
>
> I put this in my -next branch, so we'll at least have a chance of
> making a linux-next cycle before v3.7 pops.
Great. Thx!
>
> >>> ---
> >>> drivers/pci/xen-pcifront.c | 5 ++++-
> >>> 1 files changed, 4 insertions(+), 1 deletions(-)
> >>>
> >>> diff --git a/drivers/pci/xen-pcifront.c b/drivers/pci/xen-pcifront.c
> >>> index 0aab85a..a0c7312 100644
> >>> --- a/drivers/pci/xen-pcifront.c
> >>> +++ b/drivers/pci/xen-pcifront.c
> >>> @@ -1068,13 +1068,16 @@ static void __init_refok pcifront_backend_changed(struct xenbus_device *xdev,
> >>> case XenbusStateInitialising:
> >>> case XenbusStateInitWait:
> >>> case XenbusStateInitialised:
> >>> - case XenbusStateClosed:
> >>> break;
> >>>
> >>> case XenbusStateConnected:
> >>> pcifront_try_connect(pdev);
> >>> break;
> >>>
> >>> + case XenbusStateClosed:
> >>> + if (xdev->state == XenbusStateClosed)
> >>> + break;
> >>> + /* Missed the backend's CLOSING state -- fallthrough */
> >>> case XenbusStateClosing:
> >>> dev_warn(&xdev->dev, "backend going away!\n");
> >>> pcifront_try_disconnect(pdev);
> >>> --
> >>> 1.7.2.5
next prev parent reply other threads:[~2012-11-30 22:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 10:02 [PATCH 0/5] drivers: xen frontend devices should handle missed backend CLOSING David Vrabel
2012-10-18 10:02 ` David Vrabel
2012-10-18 10:02 ` David Vrabel
2012-10-18 10:03 ` [PATCH 1/5] xen-netfront: handle backend CLOSED without CLOSING David Vrabel
2012-10-18 10:03 ` [PATCH 2/5] xen-blkfront: " David Vrabel
2012-10-18 10:03 ` [PATCH 3/5] xen-pcifront: " David Vrabel
2012-10-19 12:59 ` Konrad Rzeszutek Wilk
2012-11-30 18:41 ` Bjorn Helgaas
2012-11-30 21:42 ` Bjorn Helgaas
2012-11-30 22:39 ` Konrad Rzeszutek Wilk [this message]
2012-10-18 10:03 ` [PATCH 4/5] xen-fbfront: " David Vrabel
2012-10-18 10:03 ` David Vrabel
2012-10-19 13:00 ` Konrad Rzeszutek Wilk
2012-10-19 13:00 ` Konrad Rzeszutek Wilk
2012-10-23 4:50 ` Florian Tobias Schandinat
2012-10-23 4:50 ` Florian Tobias Schandinat
2012-10-18 10:03 ` [PATCH 5/5] xen-kbdfront: " David Vrabel
2012-10-19 13:00 ` Konrad Rzeszutek Wilk
2012-10-19 13:00 ` Konrad Rzeszutek Wilk
2012-10-19 16:34 ` Dmitry Torokhov
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=20121130223939.GA7749@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=bhelgaas@google.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=xen-devel@lists.xen.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.