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>
Subject: [PATCH v2 0/3] loop: LO_FLAGS_BLOCKSIZE fixes
Date: Fri, 18 Aug 2017 12:27:34 -0700 [thread overview]
Message-ID: <cover.1503084216.git.osandov@fb.com> (raw)
From: Omar Sandoval <osandov@fb.com>
Patches 1 and 3 are from the original series.
Patch 2 gets rid of the redundant struct loop_device.lo_logical_blocksize
in favor of using the queue's own logical_block_size. Karel, I decided
against adding another sysfs entry since it will always be the same as
queue/logical_block_size, is that alright with you?
Omar Sandoval (3):
loop: fix hang if LOOP_SET_STATUS gets invalid blocksize or encrypt
type
loop: use queue limit instead of private lo_logical_blocksize
loop: always return block size in LOOP_GET_STATUS
drivers/block/loop.c | 71 ++++++++++++++++++++++++++--------------------------
drivers/block/loop.h | 1 -
2 files changed, 36 insertions(+), 36 deletions(-)
--
2.14.1
next reply other threads:[~2017-08-18 19:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 19:27 Omar Sandoval [this message]
2017-08-18 19:27 ` [PATCH v2 1/3] loop: fix hang if LOOP_SET_STATUS gets invalid blocksize or encrypt type Omar Sandoval
2017-08-18 19:27 ` [PATCH v2 2/3] loop: use queue limit instead of private lo_logical_blocksize Omar Sandoval
2017-08-21 5:58 ` Hannes Reinecke
2017-08-21 16:45 ` Omar Sandoval
2017-08-18 19:27 ` [PATCH v2 3/3] loop: always return block size in LOOP_GET_STATUS Omar Sandoval
2017-08-21 5:59 ` Hannes Reinecke
2017-08-22 10:53 ` [PATCH v2 0/3] loop: LO_FLAGS_BLOCKSIZE fixes Milan Broz
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.1503084216.git.osandov@fb.com \
--to=osandov@osandov.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.