From: Juergen Gross <jgross@suse.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
xen-devel@lists.xenproject.org
Subject: [PATCH 0/2] xen/xenbus: better handle backend crash
Date: Thu, 12 Feb 2026 09:38:24 +0100 [thread overview]
Message-ID: <20260212083826.136221-1-jgross@suse.com> (raw)
This small series fixes PV-device frontend side handling in case the
backend crashed and has come up again.
The old device will be discarded and the replacement can be used
instead.
Juergen Gross (2):
xenbus: add xenbus_device parameter to xenbus_read_driver_state()
xen/xenbus: better handle backend crash
drivers/net/xen-netfront.c | 34 +++++++++---------
drivers/pci/xen-pcifront.c | 8 ++---
drivers/scsi/xen-scsifront.c | 2 +-
drivers/xen/xen-pciback/xenbus.c | 10 +++---
drivers/xen/xenbus/xenbus_client.c | 16 +++++++--
drivers/xen/xenbus/xenbus_probe.c | 42 ++++++++++++++++++++--
drivers/xen/xenbus/xenbus_probe_frontend.c | 2 +-
include/xen/xenbus.h | 4 ++-
8 files changed, 83 insertions(+), 35 deletions(-)
--
2.53.0
next reply other threads:[~2026-02-12 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 8:38 Juergen Gross [this message]
2026-02-12 8:38 ` [PATCH 1/2] xenbus: add xenbus_device parameter to xenbus_read_driver_state() Juergen Gross
2026-02-12 14:04 ` kernel test robot
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=20260212083826.136221-1-jgross@suse.com \
--to=jgross@suse.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=oleksandr_tyshchenko@epam.com \
--cc=pabeni@redhat.com \
--cc=sstabellini@kernel.org \
--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