All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, virtualization@lists.linux-foundation.org
Cc: f.hetzelt@tu-berlin.de, linux-kernel@vger.kernel.org,
	david.kaplan@amd.com, konrad.wilk@oracle.com
Subject: [PATCH V4 0/4] Validate used buffer length
Date: Tue, 26 Oct 2021 15:19:56 +0800	[thread overview]
Message-ID: <20211026072000.8699-1-jasowang@redhat.com> (raw)

Hi All:

This patch tries to validate the used buffer length in the virtio
core. This help to eliminate the unexpected result caused by buggy or
mailicous devices. For the drivers that can do the validation itself,
they can ask the virtio core to suppress the check.

Changes since V3:

- Initialize the buflen to zero when the validation is done by the driver.

Jason Wang (4):
  virtio_ring: validate used buffer length
  virtio-net: don't let virtio core to validate used length
  virtio-blk: don't let virtio core to validate used length
  virtio-scsi: don't let virtio core to validate used buffer length

 drivers/block/virtio_blk.c   |  1 +
 drivers/net/virtio_net.c     |  1 +
 drivers/scsi/virtio_scsi.c   |  1 +
 drivers/virtio/virtio_ring.c | 60 ++++++++++++++++++++++++++++++++++++
 include/linux/virtio.h       |  2 ++
 5 files changed, 65 insertions(+)

-- 
2.25.1

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, virtualization@lists.linux-foundation.org
Cc: linux-kernel@vger.kernel.org, f.hetzelt@tu-berlin.de,
	david.kaplan@amd.com, konrad.wilk@oracle.com,
	Jason Wang <jasowang@redhat.com>
Subject: [PATCH V4 0/4] Validate used buffer length
Date: Tue, 26 Oct 2021 15:19:56 +0800	[thread overview]
Message-ID: <20211026072000.8699-1-jasowang@redhat.com> (raw)

Hi All:

This patch tries to validate the used buffer length in the virtio
core. This help to eliminate the unexpected result caused by buggy or
mailicous devices. For the drivers that can do the validation itself,
they can ask the virtio core to suppress the check.

Changes since V3:

- Initialize the buflen to zero when the validation is done by the driver.

Jason Wang (4):
  virtio_ring: validate used buffer length
  virtio-net: don't let virtio core to validate used length
  virtio-blk: don't let virtio core to validate used length
  virtio-scsi: don't let virtio core to validate used buffer length

 drivers/block/virtio_blk.c   |  1 +
 drivers/net/virtio_net.c     |  1 +
 drivers/scsi/virtio_scsi.c   |  1 +
 drivers/virtio/virtio_ring.c | 60 ++++++++++++++++++++++++++++++++++++
 include/linux/virtio.h       |  2 ++
 5 files changed, 65 insertions(+)

-- 
2.25.1


             reply	other threads:[~2021-10-26  7:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  7:19 Jason Wang [this message]
2021-10-26  7:19 ` [PATCH V4 0/4] Validate used buffer length Jason Wang
2021-10-26  7:19 ` [PATCH V4 1/4] virtio_ring: validate " Jason Wang
2021-10-26  7:19   ` Jason Wang
2021-10-26  9:43   ` Michael S. Tsirkin
2021-10-26  9:43     ` Michael S. Tsirkin
2021-10-26 10:21     ` Jason Wang
2021-10-26 10:21       ` Jason Wang
2021-10-26 10:32       ` Michael S. Tsirkin
2021-10-26 10:32         ` Michael S. Tsirkin
2021-10-26  7:19 ` [PATCH V4 2/4] virtio-net: don't let virtio core to validate used length Jason Wang
2021-10-26  7:19   ` Jason Wang
2021-10-26  7:19 ` [PATCH V4 3/4] virtio-blk: " Jason Wang
2021-10-26  7:19   ` Jason Wang
2021-10-26  7:20 ` [PATCH V4 4/4] virtio-scsi: don't let virtio core to validate used buffer length Jason Wang
2021-10-26  7:20   ` Jason Wang

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=20211026072000.8699-1-jasowang@redhat.com \
    --to=jasowang@redhat.com \
    --cc=david.kaplan@amd.com \
    --cc=f.hetzelt@tu-berlin.de \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux-foundation.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.