From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
David Vrabel <david.vrabel@citrix.com>,
Laszlo Ersek <lersek@redhat.com>,
Andrew Jones <drjones@redhat.com>, Jeff Moyer <jmoyer@redhat.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Subject: Re: [PATCH RESEND] xen/blkfront: improve protection against issuing unsupported REQ_FUA
Date: Wed, 03 Dec 2014 18:05:42 +0100 [thread overview]
Message-ID: <87wq68k6jd.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <547F40FC.7030403@oracle.com> (Boris Ostrovsky's message of "Wed, 03 Dec 2014 11:57:32 -0500")
Boris Ostrovsky <boris.ostrovsky@oracle.com> writes:
> On 12/01/2014 08:01 AM, Vitaly Kuznetsov wrote:
>> Guard against issuing unsupported REQ_FUA and REQ_FLUSH was introduced
>> in d11e61583 and was factored out into blkif_request_flush_valid() in
>> 0f1ca65ee. However:
>> 1) This check in incomplete. In case we negotiated to feature_flush = REQ_FLUSH
>> and flush_op = BLKIF_OP_FLUSH_DISKCACHE (so FUA is unsupported) FUA request
>> will still pass the check.
>> 2) blkif_request_flush_valid() is misnamed. It is bool but returns true when
>> the request is invalid.
>> 3) When blkif_request_flush_valid() fails -EIO is being returned. It seems that
>> -EOPNOTSUPP is more appropriate here.
>> Fix all of the above issues.
>>
>> This patch is based on the original patch by Laszlo Ersek and a comment by
>> Jeff Moyer.
>>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
>
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>
> (although, as I mentioned last time, a companion patch to remove
> flush_op would be a good thing to have)
>
Thanks, it is on my todo list but I'm trying to separate this
(potential) bugfix from straight cleanup.
> -boris
>
>> ---
>> drivers/block/xen-blkfront.c | 14 ++++++++------
>> 1 file changed, 8 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/block/xen-blkfront.c b/drivers/block/xen-blkfront.c
>> index 5ac312f..2e6c103 100644
>> --- a/drivers/block/xen-blkfront.c
>> +++ b/drivers/block/xen-blkfront.c
>> @@ -582,12 +582,14 @@ static inline void flush_requests(struct blkfront_info *info)
>> notify_remote_via_irq(info->irq);
>> }
>> -static inline bool blkif_request_flush_valid(struct request *req,
>> - struct blkfront_info *info)
>> +static inline bool blkif_request_flush_invalid(struct request *req,
>> + struct blkfront_info *info)
>> {
>> return ((req->cmd_type != REQ_TYPE_FS) ||
>> - ((req->cmd_flags & (REQ_FLUSH | REQ_FUA)) &&
>> - !info->flush_op));
>> + ((req->cmd_flags & REQ_FLUSH) &&
>> + !(info->feature_flush & REQ_FLUSH)) ||
>> + ((req->cmd_flags & REQ_FUA) &&
>> + !(info->feature_flush & REQ_FUA)));
>> }
>> /*
>> @@ -612,8 +614,8 @@ static void do_blkif_request(struct request_queue *rq)
>> blk_start_request(req);
>> - if (blkif_request_flush_valid(req, info)) {
>> - __blk_end_request_all(req, -EIO);
>> + if (blkif_request_flush_invalid(req, info)) {
>> + __blk_end_request_all(req, -EOPNOTSUPP);
>> continue;
>> }
>>
--
Vitaly
next prev parent reply other threads:[~2014-12-03 17:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 13:44 [PATCH] xen/blkfront: improve protection against issuing unsupported REQ_FUA Vitaly Kuznetsov
2014-11-03 12:22 ` Laszlo Ersek
2014-11-03 15:49 ` Boris Ostrovsky
2014-11-03 15:49 ` Boris Ostrovsky
2014-11-03 17:11 ` Vitaly Kuznetsov
2014-11-03 17:11 ` Vitaly Kuznetsov
2014-11-03 12:22 ` Laszlo Ersek
2014-12-01 13:01 ` [PATCH RESEND] " Vitaly Kuznetsov
2014-12-03 16:57 ` Boris Ostrovsky
2014-12-03 17:05 ` Vitaly Kuznetsov
2014-12-03 17:05 ` Vitaly Kuznetsov [this message]
2014-12-03 16:57 ` Boris Ostrovsky
2014-12-01 13:01 ` Vitaly Kuznetsov
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=87wq68k6jd.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=drjones@redhat.com \
--cc=jmoyer@redhat.com \
--cc=konrad.wilk@oracle.com \
--cc=lersek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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.