stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Andrey Grodzovsky <andrey2805@gmail.com>,
	<xen-devel@lists.xenproject.org>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	<stable@vger.kernel.org>, Jan Beulich <JBeulich@suse.com>,
	<jw@quattru.com>
Subject: Re: [Xen-devel] [PATCH] xen/pciback: Fix conf_space read/write overlap check.
Date: Tue, 21 Jun 2016 18:15:00 +0100	[thread overview]
Message-ID: <57697614.5020003@citrix.com> (raw)
In-Reply-To: <1466519876-7205-1-git-send-email-andrey2805@gmail.com>

On 21/06/16 15:37, Andrey Grodzovsky wrote:
> Current overlap check is evaluating to false a case where a filter field
> is fully contained (proper subset) of a r/w request.
> This change applies classical overlap check instead to include
> all the scenarios.

Reviewed-by: David Vrabel <david.vrabel@citrix.com>

But the commit message could do with a concrete example of an access
that failed.

David

> 
> Related to https://www.mail-archive.com/xen-devel@lists.xen.org/msg72174.html
> 
> Cc: Jan Beulich <JBeulich@suse.com>
> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Andrey Grodzovsky <andrey2805@gmail.com>
> ---
>  drivers/xen/xen-pciback/conf_space.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/xen/xen-pciback/conf_space.c b/drivers/xen/xen-pciback/conf_space.c
> index 8e67336..6a25533 100644
> --- a/drivers/xen/xen-pciback/conf_space.c
> +++ b/drivers/xen/xen-pciback/conf_space.c
> @@ -183,8 +183,7 @@ int xen_pcibk_config_read(struct pci_dev *dev, int offset, int size,
>  		field_start = OFFSET(cfg_entry);
>  		field_end = OFFSET(cfg_entry) + field->size;
>  
> -		if ((req_start >= field_start && req_start < field_end)
> -		    || (req_end > field_start && req_end <= field_end)) {
> +		 if (req_end > field_start && field_end > req_start) {
>  			err = conf_space_read(dev, cfg_entry, field_start,
>  					      &tmp_val);
>  			if (err)
> @@ -230,8 +229,7 @@ int xen_pcibk_config_write(struct pci_dev *dev, int offset, int size, u32 value)
>  		field_start = OFFSET(cfg_entry);
>  		field_end = OFFSET(cfg_entry) + field->size;
>  
> -		if ((req_start >= field_start && req_start < field_end)
> -		    || (req_end > field_start && req_end <= field_end)) {
> +		 if (req_end > field_start && field_end > req_start) {
>  			tmp_val = 0;
>  
>  			err = xen_pcibk_config_read(dev, field_start,
> 


  parent reply	other threads:[~2016-06-21 17:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 14:37 [PATCH] xen/pciback: Fix conf_space read/write overlap check Andrey Grodzovsky
2016-06-21 15:52 ` Boris Ostrovsky
2016-06-22  4:11   ` Juergen Gross
2016-06-21 17:15 ` David Vrabel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-21 18:26 Andrey Grodzovsky
2016-06-23  9:56 ` [Xen-devel] " David Vrabel

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=57697614.5020003@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrey2805@gmail.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jw@quattru.com \
    --cc=stable@vger.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;
as well as URLs for NNTP newsgroup(s).