From: Jeff Cody <jcody@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.8? 3/3] block/curl: Drop TFTP "support"
Date: Wed, 2 Nov 2016 14:22:34 -0400 [thread overview]
Message-ID: <20161102182234.GC6642@localhost.localdomain> (raw)
In-Reply-To: <20161102175539.4375-4-mreitz@redhat.com>
On Wed, Nov 02, 2016 at 06:55:39PM +0100, Max Reitz wrote:
> Because TFTP does not support byte ranges, it was never usable with our
> curl block driver. Since apparently nobody has ever complained loudly
> enough for someone to take care of the issue until now, it seems
> reasonable to assume that nobody has ever actually used it.
>
> Therefore, it should be safe to just drop it from curl's protocol list.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> block/curl.c | 20 +-------------------
> 1 file changed, 1 insertion(+), 19 deletions(-)
>
> diff --git a/block/curl.c b/block/curl.c
> index e5eaa7b..ba8adae 100644
> --- a/block/curl.c
> +++ b/block/curl.c
> @@ -68,8 +68,7 @@ static CURLMcode __curl_multi_socket_action(CURLM *multi_handle,
> #endif
>
> #define PROTOCOLS (CURLPROTO_HTTP | CURLPROTO_HTTPS | \
> - CURLPROTO_FTP | CURLPROTO_FTPS | \
> - CURLPROTO_TFTP)
> + CURLPROTO_FTP | CURLPROTO_FTPS)
>
> #define CURL_NUM_STATES 8
> #define CURL_NUM_ACB 8
> @@ -886,29 +885,12 @@ static BlockDriver bdrv_ftps = {
> .bdrv_attach_aio_context = curl_attach_aio_context,
> };
>
> -static BlockDriver bdrv_tftp = {
> - .format_name = "tftp",
> - .protocol_name = "tftp",
> -
> - .instance_size = sizeof(BDRVCURLState),
> - .bdrv_parse_filename = curl_parse_filename,
> - .bdrv_file_open = curl_open,
> - .bdrv_close = curl_close,
> - .bdrv_getlength = curl_getlength,
> -
> - .bdrv_aio_readv = curl_aio_readv,
> -
> - .bdrv_detach_aio_context = curl_detach_aio_context,
> - .bdrv_attach_aio_context = curl_attach_aio_context,
> -};
> -
> static void curl_block_init(void)
> {
> bdrv_register(&bdrv_http);
> bdrv_register(&bdrv_https);
> bdrv_register(&bdrv_ftp);
> bdrv_register(&bdrv_ftps);
> - bdrv_register(&bdrv_tftp);
> }
>
> block_init(curl_block_init);
> --
> 2.10.2
>
Reviewed-by: Jeff Cody <jcody@redhat.com>
next prev parent reply other threads:[~2016-11-02 18:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 17:55 [Qemu-devel] [PATCH for-2.8? 0/3] block/curl: Drop TFTP "support" Max Reitz
2016-11-02 17:55 ` [Qemu-devel] [PATCH for-2.8? 1/3] qemu-options: Drop mentions of curl's TFTP support Max Reitz
2016-11-02 18:20 ` Jeff Cody
2016-11-02 17:55 ` [Qemu-devel] [PATCH for-2.8? 2/3] qapi: Drop curl's TFTP protocol Max Reitz
2016-11-02 18:22 ` Jeff Cody
2016-11-02 17:55 ` [Qemu-devel] [PATCH for-2.8? 3/3] block/curl: Drop TFTP "support" Max Reitz
2016-11-02 18:22 ` Jeff Cody [this message]
2016-11-02 18:20 ` [Qemu-devel] [PATCH for-2.8? 0/3] " Jeff Cody
2016-11-03 7:56 ` Markus Armbruster
2016-11-04 16:53 ` Max Reitz
2016-11-07 8:20 ` Markus Armbruster
2016-11-07 15:42 ` Max Reitz
2016-11-08 7:14 ` Markus Armbruster
2016-11-09 19:15 ` Jeff Cody
2016-11-11 19:46 ` Max Reitz
2016-11-14 18:54 ` Jeff Cody
2016-11-03 9:42 ` Kevin Wolf
2016-11-07 12:57 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
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=20161102182234.GC6642@localhost.localdomain \
--to=jcody@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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 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).