From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, blauwirbel@gmail.com, brad@comstyle.com
Subject: Re: [Qemu-devel] Tree broken by nbd: support feature negotiation commit.
Date: Wed, 21 Sep 2011 11:21:54 +0200 [thread overview]
Message-ID: <1316596914-9570-1-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <4E7995B3.3030106@comstyle.com>
On 09/21/2011 09:43 AM, Brad wrote:
>> It is not portable code, and (unlike the rest of qemu-nbd and the
>> block/nbd.c protocol) not meant to be portable. Are BLKROSET (defined in
>> linux/fs.h) and the whole set of NBD ioctls available under OpenBSD?
>
> Ok. What confused me a bit is that particular code path before your
> commit was being built on anything but Windows but is now Linux only.
> No we don't have BLKROSET. So am I to understand that even before this
> particular commit that this code was only supported on Linux?
Yes.
Here's a fix.
Paolo
----------------------- 8< -----------------------
From: Paolo Bonzini <pbonzini@redhat.com>
Date: Wed, 21 Sep 2011 09:34:12 +0200
Subject: [PATCH] nbd: fix non-Linux build failure
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
nbd.c | 29 ++++++++++++-----------------
1 files changed, 12 insertions(+), 17 deletions(-)
diff --git a/nbd.c b/nbd.c
index 595f4d8..9810f99 100644
--- a/nbd.c
+++ b/nbd.c
@@ -437,7 +447,7 @@ int nbd_client(int fd)
return ret;
}
#else
-int nbd_init(int fd, int csock, off_t size, size_t blocksize)
+int nbd_init(int fd, int csock, uint32_t flags, off_t size, size_t blocksize)
{
errno = ENOTSUP;
return -1;
--
1.7.6
next prev parent reply other threads:[~2011-09-21 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 7:27 [Qemu-devel] Tree broken by nbd: support feature negotiation commit Brad
2011-09-21 7:32 ` Paolo Bonzini
2011-09-21 7:42 ` Kevin Wolf
2011-09-21 7:43 ` Brad
2011-09-21 9:21 ` Paolo Bonzini [this message]
2011-09-21 9:23 ` Brad
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=1316596914-9570-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=brad@comstyle.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.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 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).