public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
	xen-devel@lists.xenproject.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2 0/4] xen/pv-scsi: update header and harden frontend
Date: Fri, 29 Apr 2022 18:25:42 -0400	[thread overview]
Message-ID: <fdb13c95-acde-ebac-9864-e661d7daeeb7@oracle.com> (raw)
In-Reply-To: <20220428075323.12853-1-jgross@suse.com>


On 4/28/22 3:53 AM, Juergen Gross wrote:
> Update the Xen PV-scsi interface from the Xen tree and adapt the
> related drivers to use the new definitions.
>
> Harden the frontend driver to be no longer vulnerable to a malicious
> backend.
>
> Juergen Gross (4):
>    xen: update vscsiif.h
>    xen/scsiback: use new command result macros
>    xen/scsifront: use new command result macros
>    xen/scsifront: harden driver against malicious backend
>
>   drivers/scsi/xen-scsifront.c       | 168 ++++++++++++++++++++++-------
>   drivers/xen/xen-scsiback.c         |  82 +++++++++++++-
>   include/xen/interface/io/vscsiif.h | 133 ++++++++++++++++++++++-
>   3 files changed, 340 insertions(+), 43 deletions(-)


Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>


      parent reply	other threads:[~2022-04-29 22:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  7:53 [PATCH v2 0/4] xen/pv-scsi: update header and harden frontend Juergen Gross
2022-04-28  7:53 ` [PATCH v2 1/4] xen: update vscsiif.h Juergen Gross
2022-04-28  7:53 ` [PATCH v2 2/4] xen/scsiback: use new command result macros Juergen Gross
2022-04-28  7:53 ` [PATCH v2 3/4] xen/scsifront: " Juergen Gross
2022-04-28  7:53 ` [PATCH v2 4/4] xen/scsifront: harden driver against malicious backend Juergen Gross
2022-04-29 22:25 ` Boris Ostrovsky [this message]

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=fdb13c95-acde-ebac-9864-e661d7daeeb7@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=jejb@linux.ibm.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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