From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Dwayne Litzenberger" <dlitz@dlitz.net>
Subject: [PATCH 1/2] xen-pciback: Fix error return in bar_write() and rom_write()
Date: Sun, 2 Dec 2018 18:47:32 +0100 [thread overview]
Message-ID: <f5ea0f3c2e29a96b59e409e4ae4c62de11a05fc8.1543772656.git-series.marmarek@invisiblethingslab.com> (raw)
In-Reply-To: <cover.55c0e31b75e2fbdf4206cc39c2fd7581793ae7ae.1543772656.git-series.marmarek@invisiblethingslab.com>
In-Reply-To: <cover.55c0e31b75e2fbdf4206cc39c2fd7581793ae7ae.1543772656.git-series.marmarek@invisiblethingslab.com>
From: Dwayne Litzenberger <dlitz@dlitz.net>
Signed-off-by: Dwayne Litzenberger <dlitz@dlitz.net>
---
| 24 ++++++++++++++++------
1 file changed, 18 insertions(+), 6 deletions(-)
--git a/drivers/xen/xen-pciback/conf_space_header.c b/drivers/xen/xen-pciback/conf_space_header.c
index 10ae24b..697d0a8 100644
--- a/drivers/xen/xen-pciback/conf_space_header.c
+++ b/drivers/xen/xen-pciback/conf_space_header.c
@@ -135,6 +135,7 @@ static int command_write(struct pci_dev *dev, int offset, u16 value, void *data)
static int rom_write(struct pci_dev *dev, int offset, u32 value, void *data)
{
+ int err = 0;
struct pci_bar_info *bar = data;
if (unlikely(!bar)) {
@@ -150,17 +151,22 @@ static int rom_write(struct pci_dev *dev, int offset, u32 value, void *data)
bar->which = 1;
else {
u32 tmpval;
- pci_read_config_dword(dev, offset, &tmpval);
+ err = pci_read_config_dword(dev, offset, &tmpval);
+ if (err)
+ goto out;
if (tmpval != bar->val && value == bar->val) {
/* Allow restoration of bar value. */
- pci_write_config_dword(dev, offset, bar->val);
+ err = pci_write_config_dword(dev, offset, bar->val);
+ if (err)
+ goto out;
}
bar->which = 0;
}
/* Do we need to support enabling/disabling the rom address here? */
- return 0;
+out:
+ return err;
}
/* For the BARs, only allow writes which write ~0 or
@@ -169,6 +175,7 @@ static int rom_write(struct pci_dev *dev, int offset, u32 value, void *data)
*/
static int bar_write(struct pci_dev *dev, int offset, u32 value, void *data)
{
+ int err = 0;
struct pci_bar_info *bar = data;
unsigned int pos = (offset - PCI_BASE_ADDRESS_0) / 4;
const struct resource *res = dev->resource;
@@ -193,15 +200,20 @@ static int bar_write(struct pci_dev *dev, int offset, u32 value, void *data)
bar->which = 1;
else {
u32 tmpval;
- pci_read_config_dword(dev, offset, &tmpval);
+ err = pci_read_config_dword(dev, offset, &tmpval);
+ if (err)
+ goto out;
if (tmpval != bar->val && value == bar->val) {
/* Allow restoration of bar value. */
- pci_write_config_dword(dev, offset, bar->val);
+ err = pci_write_config_dword(dev, offset, bar->val);
+ if (err)
+ goto out;
}
bar->which = 0;
}
- return 0;
+out:
+ return err;
}
static int bar_read(struct pci_dev *dev, int offset, u32 * value, void *data)
--
git-series 0.9.1
next prev parent reply other threads:[~2018-12-02 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 17:47 [PATCH 0/2] xen-paciback: Fixes for PCI passthrough of AMD GPU Marek Marczykowski-Górecki
2018-12-02 17:47 ` Marek Marczykowski-Górecki [this message]
2018-12-03 10:55 ` [Xen-devel] [PATCH 1/2] xen-pciback: Fix error return in bar_write() and rom_write() Jan Beulich
2018-12-03 12:35 ` Roger Pau Monné
2018-12-02 17:47 ` [PATCH 2/2] xen-pciback: Allow enabling/disabling expansion ROM Marek Marczykowski-Górecki
2018-12-03 11:01 ` [Xen-devel] " Jan Beulich
2018-12-03 14:47 ` Marek Marczykowski
2018-12-03 15:04 ` Jan Beulich
2018-12-03 12:53 ` Roger Pau Monné
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=f5ea0f3c2e29a96b59e409e4ae4c62de11a05fc8.1543772656.git-series.marmarek@invisiblethingslab.com \
--to=marmarek@invisiblethingslab.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dlitz@dlitz.net \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®