All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Ashijeet Acharya <ashijeetacharya@gmail.com>
Cc: jcody@redhat.com, QEMU Developers <qemu-devel@nongnu.org>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] block/ssh:Allow blockdev-add for ssh
Date: Thu, 29 Sep 2016 09:07:47 +0100	[thread overview]
Message-ID: <20160929080747.GR26315@redhat.com> (raw)
In-Reply-To: <CAC2QTZbtfrJ-pgs2L1+_8NvVREap+aJDztTvVn+hBjAe0a2iLg@mail.gmail.com>

On Thu, Sep 29, 2016 at 01:05:48PM +0530, Ashijeet Acharya wrote:
> Hi all,
> 
> I was trying to convert SSH driver to support 'blockdev-add' and so
> far I have tried to figure out what the struct 'BlockdevOptionsSsh' in
> block-core.json should look like,
> 
> { 'struct': 'BlockdevOptionsSsh',
>   'data': { 'tcp': 'InetSocketAddress',
>              'path': 'str' } }
> 
> Naive question but I have to ask, Am I missing something?
> 
> As far as I know, ssh only supports 'tcp' right? So using
> 'InetSocketAddress' should be good enough. (like the TODO says)
> 
> I had a discussion with Kevin about this and he thinks, maybe
> 'SocketAddress' can be used too because the restriction comes from the
> qemu block driver rather than the backend. He advised me to get an
> opinion on this one from the maintainers of SSH.

I have no idea.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW

  reply	other threads:[~2016-09-29  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29  7:35 [Qemu-devel] block/ssh:Allow blockdev-add for ssh Ashijeet Acharya
2016-09-29  8:07 ` Richard W.M. Jones [this message]
2016-09-29 10:42   ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2016-09-29 11:07     ` Daniel P. Berrange
2016-09-29 11:15       ` Kevin Wolf
2016-09-29 11:22     ` Daniel P. Berrange
2016-09-29 11:36       ` Kevin Wolf
2016-09-29 11:59         ` Richard W.M. Jones
2016-09-29 14:07           ` Ashijeet Acharya
2016-09-29 15:02             ` Kevin Wolf
2016-09-29 18:32               ` Ashijeet Acharya

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=20160929080747.GR26315@redhat.com \
    --to=rjones@redhat.com \
    --cc=ashijeetacharya@gmail.com \
    --cc=jcody@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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 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.