From: Max Reitz <mreitz@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, benoit@irqsave.net,
ronniesahlberg@gmail.com, armbru@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCHv5 6/6] block/iscsi: check for oversized requests
Date: Mon, 27 Oct 2014 09:35:32 +0100 [thread overview]
Message-ID: <544E03D4.5090004@redhat.com> (raw)
In-Reply-To: <1414253919-3044-7-git-send-email-pl@kamp.de>
On 2014-10-25 at 18:18, Peter Lieven wrote:
> Cancel oversized requests early. They would generate
> an iSCSI protocol error anyway; after having transferred
> possibly a lot of data over the wire.
>
> Suggested-By: Max Reitz <mreitz@redhat.com>
> Signed-off-by: Peter Lieven <pl@kamp.de>
> ---
> block/iscsi.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/block/iscsi.c b/block/iscsi.c
> index 85131b7..8747fc3 100644
> --- a/block/iscsi.c
> +++ b/block/iscsi.c
> @@ -367,6 +367,12 @@ static int coroutine_fn iscsi_co_writev(BlockDriverState *bs,
> return -EINVAL;
> }
>
> + if (bs->bl.max_transfer_length && nb_sectors > bs->bl.max_transfer_length) {
> + error_report("iSCSI Error: Write of %d sectors exceeds max_xfer_len "
> + "of %d sectors.", nb_sectors, bs->bl.max_transfer_length);
> + return -EINVAL;
> + }
> +
> lba = sector_qemu2lun(sector_num, iscsilun);
> num_sectors = sector_qemu2lun(nb_sectors, iscsilun);
> iscsi_co_init_iscsitask(iscsilun, &iTask);
> @@ -534,6 +540,12 @@ static int coroutine_fn iscsi_co_readv(BlockDriverState *bs,
> return -EINVAL;
> }
>
> + if (bs->bl.max_transfer_length && nb_sectors > bs->bl.max_transfer_length) {
> + error_report("iSCSI Error: Read of %d sectors exceeds max_xfer_len "
> + "of %d sectors.", nb_sectors, bs->bl.max_transfer_length);
> + return -EINVAL;
> + }
> +
> if (iscsilun->lbprz && nb_sectors >= ISCSI_CHECKALLOC_THRES &&
> !iscsi_allocationmap_is_allocated(iscsilun, sector_num, nb_sectors)) {
> int64_t ret;
I think to remember someone telling me there should not be full stops at
the end of error messages. I can cope with it, though.
Reviewed-by: Max Reitz <mreitz@redhat.com>
prev parent reply other threads:[~2014-10-27 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 16:18 [Qemu-devel] [PATCHv5 0/6] introduce max_transfer_length Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 1/6] util: introduce MIN_NON_ZERO Peter Lieven
2014-10-27 8:24 ` Max Reitz
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 2/6] BlockLimits: introduce max_transfer_length Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 3/6] block/iscsi: set max_transfer_length Peter Lieven
2014-10-27 8:28 ` Max Reitz
2014-10-27 8:36 ` Peter Lieven
2014-10-27 8:44 ` Max Reitz
2014-10-27 8:47 ` Peter Lieven
2014-10-27 9:04 ` Max Reitz
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 4/6] block: avoid creating oversized writes in multiwrite_merge Peter Lieven
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 5/6] block/iscsi: limit to INT_MAX throughout iscsi_refresh_limits Peter Lieven
2014-10-27 8:32 ` Max Reitz
2014-10-27 8:35 ` Peter Lieven
2014-10-27 8:38 ` Max Reitz
2014-10-25 16:18 ` [Qemu-devel] [PATCHv5 6/6] block/iscsi: check for oversized requests Peter Lieven
2014-10-27 8:35 ` Max Reitz [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=544E03D4.5090004@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=benoit@irqsave.net \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).