From: Eric Blake <eblake@redhat.com>
To: Alex Bligh <alex@alex.org.uk>
Cc: "nbd-general@lists.sourceforge.net"
<nbd-general@lists.sourceforge.net>, Wouter Verhelst <w@uter.be>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 2/2] Correct definition of NBD_CMD_FLAG_FUA
Date: Thu, 31 Mar 2016 14:07:01 -0600 [thread overview]
Message-ID: <56FD8365.5020709@redhat.com> (raw)
In-Reply-To: <22F045FF-5560-443D-98C0-D634FC0985E1@alex.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On 03/31/2016 01:25 PM, Alex Bligh wrote:
>
> On 31 Mar 2016, at 20:14, Eric Blake <eblake@redhat.com> wrote:
>
>>>
>>>
>>> Should we produce a new name for it (and future command flags)
>>> that aren't shifted left 16 places, and just maintain the
>>> current value for compatibility?
>>
>> I don't see the point. Your fix looks correct.
>
> OK. And the wrongness hasn't yet got into /usr/include/linux/nbd.h
Still using the older '__be32 type;' instead of the newer '__be16 flags;
__be16 type;', changing that one will be ABI compatible, but not API
compatible. I don't know what people want to do there, :(
> or include/uapi/linux/nbd.h ; these have no reference to FUA at all,
I'm not finding that file on my system; not sure what it contains, or
where it is maintained.
> even though it does have NBD_FLAG_SEND_FLUSH, which is odd as I added
> both flags at the same time.
>
> So I'm guessing it's safe.
>
> --
> Alex Bligh
>
>
>
>
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-03-31 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 18:15 [Qemu-devel] [PATCH 2/2] Correct definition of NBD_CMD_FLAG_FUA Alex Bligh
2016-03-31 18:21 ` Alex Bligh
2016-03-31 19:14 ` Eric Blake
2016-03-31 19:25 ` Alex Bligh
2016-03-31 20:07 ` Eric Blake [this message]
2016-03-31 20:19 ` Alex Bligh
2016-04-01 7:59 ` [Qemu-devel] [Nbd] " Wouter Verhelst
2016-04-01 9:32 ` Alex Bligh
2016-04-01 9:43 ` Wouter Verhelst
2016-04-01 10:11 ` Alex Bligh
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=56FD8365.5020709@redhat.com \
--to=eblake@redhat.com \
--cc=alex@alex.org.uk \
--cc=nbd-general@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=w@uter.be \
/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).