All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: konrad.wilk@oracle.com, xen-devel@lists.xen.org,
	linux-kernel@vger.kernel.org, david.vrabel@citrix.com
Subject: Re: [PATCH] xen-blkfront: remove type check from blkfront_setup_discard
Date: Fri, 10 Jan 2014 17:28:00 -0500	[thread overview]
Message-ID: <52D073F0.5020400@oracle.com> (raw)
In-Reply-To: <20140110213746.GA933@aepfle.de>

On 01/10/2014 04:37 PM, Olaf Hering wrote:
> On Fri, Jan 10, Boris Ostrovsky wrote:
>
>> If the call below fails, is it safe to continue using discard feature? At
>> the least, are discard_granularity and discard_alignment guaranteed to have
>> sane/safe values?
> Its up to the toolstack to provide sane values. In the worst case
> discard fails. In this specific case the three values are optional, so
> the calls can fail. I do not know what happens if the backend device
> actually needs the values, but the frontend can not send proper discard
> requests. Hopefully it will not damage the hardware..

I don't know discard code works but it seems to me that if you pass, for 
example,  zero as discard_granularity (which may happen if 
xenbus_gather() fails) then blkdev_issue_discard() in the backend will 
set granularity to 1 and continue with discard. This may not be what the 
the guest admin requested. And he won't know about this since no error 
message is printed anywhere.

Similarly, if xenbug_gather("discard-secure") fails, I think the code 
will assume that secure discard has not been requested. I don't know 
what security implications this will have but it sounds bad to me.

I think we should at clear feature_discard and print an error in the log 
if *either* of xenbus_gather() calls fail.


-boris

  parent reply	other threads:[~2014-01-10 22:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 16:28 [PATCH] xen-blkfront: remove type check from blkfront_setup_discard Olaf Hering
2014-01-10 18:07 ` Boris Ostrovsky
2014-01-10 18:07 ` Boris Ostrovsky
2014-01-10 21:37   ` Olaf Hering
2014-01-10 22:28     ` Boris Ostrovsky
2014-01-10 22:28     ` Boris Ostrovsky [this message]
2014-01-10 22:49       ` [Xen-devel] " Olaf Hering
2014-01-10 22:57         ` Boris Ostrovsky
2014-01-10 22:57         ` [Xen-devel] " Boris Ostrovsky
2014-01-10 22:49       ` Olaf Hering
2014-01-13  9:30       ` Olaf Hering
2014-01-13 14:51         ` Boris Ostrovsky
2014-01-13 16:24           ` Konrad Rzeszutek Wilk
2014-01-13 16:24           ` Konrad Rzeszutek Wilk
2014-01-13 23:07           ` Olaf Hering
2014-01-13 23:07           ` Olaf Hering
2014-01-14  2:11             ` Boris Ostrovsky
2014-01-14 10:46               ` David Vrabel
2014-01-14 10:46               ` David Vrabel
2014-01-14  2:11             ` Boris Ostrovsky
2014-01-13 14:51         ` Boris Ostrovsky
2014-01-13  9:30       ` Olaf Hering
2014-01-10 21:37   ` Olaf Hering
  -- strict thread matches above, loose matches on Subject: below --
2014-01-10 16:28 Olaf Hering

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=52D073F0.5020400@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=xen-devel@lists.xen.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.