All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
	Christoph Hellwig <hch@lst.de>,
	Changpeng Liu <changpeng.liu@intel.com>,
	Daniel Verkamp <dverkamp@chromium.org>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [PATCH 0/2] block: fix discard merge for single max discard segment
Date: Tue, 11 Aug 2020 17:21:32 +0800	[thread overview]
Message-ID: <20200811092134.2256095-1-ming.lei@redhat.com> (raw)

Hello,

The 1st patch checks max discard segment limit in request merge code,
and one discard request failure issue is fixed for virtio_blk.

The 2nd patch fixes handling of single max discard segment for
virtio_blk, and potential memory corruption is fixed.


Ming Lei (2):
  block: respect queue limit of max discard segment
  block: virtio_blk: fix handling single range discard request

 block/blk-merge.c          | 10 ++++++++--
 drivers/block/virtio_blk.c | 23 +++++++++++++++--------
 2 files changed, 23 insertions(+), 10 deletions(-)

Cc: Christoph Hellwig <hch@lst.de>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Changpeng Liu <changpeng.liu@intel.com>
Cc: Daniel Verkamp <dverkamp@chromium.org>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>

-- 
2.25.2


             reply	other threads:[~2020-08-11  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11  9:21 Ming Lei [this message]
2020-08-11  9:21 ` [PATCH 1/2] block: respect queue limit of max discard segment Ming Lei
2020-08-11  9:21 ` [PATCH 2/2] block: virtio_blk: fix handling single range discard request Ming Lei
2020-08-11 12:30   ` Stefano Garzarella
2020-08-11 13:09     ` Ming Lei
2020-08-11 13:39       ` Stefano Garzarella
2020-08-11 13:43         ` Ming Lei
2020-08-11 14:16           ` Stefano Garzarella

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=20200811092134.2256095-1-ming.lei@redhat.com \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=changpeng.liu@intel.com \
    --cc=dverkamp@chromium.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=stefanha@redhat.com \
    /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.