All of lore.kernel.org
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: linux-block@vger.kernel.org
Cc: kernel-team@fb.com, Hannes Reinecke <hare@suse.de>,
	Ming Lei <ming.lei@redhat.com>, Karel Zak <kzak@redhat.com>,
	Milan Broz <gmazyland@gmail.com>
Subject: [PATCH v3 0/4] loop: LO_FLAGS_BLOCKSIZE fixes
Date: Tue, 22 Aug 2017 10:32:57 -0700	[thread overview]
Message-ID: <cover.1503422996.git.osandov@fb.com> (raw)

From: Omar Sandoval <osandov@fb.com>

Patches 1, 3, and 4 are the same as v2, plus added reviewed-bys and
tested-bys from Milan. Patch 2 is new.

Omar Sandoval (4):
  loop: fix hang if LOOP_SET_STATUS gets invalid blocksize or encrypt
    type
  loop: set discard and write zeroes limits in 512 byte sectors
  loop: use queue limit instead of private lo_logical_blocksize
  loop: always return block size in LOOP_GET_STATUS

 drivers/block/loop.c | 75 ++++++++++++++++++++++++++--------------------------
 drivers/block/loop.h |  1 -
 2 files changed, 37 insertions(+), 39 deletions(-)

-- 
2.14.1

             reply	other threads:[~2017-08-22 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 17:32 Omar Sandoval [this message]
2017-08-22 17:32 ` [PATCH v3 1/4] loop: fix hang if LOOP_SET_STATUS gets invalid blocksize or encrypt type Omar Sandoval
2017-08-22 17:32 ` [PATCH v3 2/4] loop: set discard and write zeroes limits in 512 byte sectors Omar Sandoval
2017-08-23  6:19   ` Hannes Reinecke
2017-08-22 17:33 ` [PATCH v3 3/4] loop: use queue limit instead of private lo_logical_blocksize Omar Sandoval
2017-08-23  9:23   ` Karel Zak
2017-08-23 16:16     ` Omar Sandoval
2017-08-22 17:33 ` [PATCH v3 4/4] loop: always return block size in LOOP_GET_STATUS Omar Sandoval
2017-08-22 20:25 ` [PATCH v3 0/4] loop: LO_FLAGS_BLOCKSIZE fixes Jens Axboe

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=cover.1503422996.git.osandov@fb.com \
    --to=osandov@osandov.com \
    --cc=gmazyland@gmail.com \
    --cc=hare@suse.de \
    --cc=kernel-team@fb.com \
    --cc=kzak@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@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.