From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Thomas Huth <thuth@redhat.com>,
sheepdog@lists.wpkg.org, qemu-block@nongnu.org,
libvir-list@redhat.com, Markus Armbruster <armbru@redhat.com>,
Max Reitz <mreitz@redhat.com>, Liu Yuan <namei.unix@gmail.com>
Subject: Re: [PATCH v2 2/2] block: deprecate the sheepdog block driver
Date: Wed, 23 Sep 2020 12:25:47 +0200 [thread overview]
Message-ID: <1d391aab-db3d-a134-9657-d81c7c2d9130@redhat.com> (raw)
In-Reply-To: <20200922161611.2049616-3-berrange@redhat.com>
On 9/22/20 6:16 PM, Daniel P. Berrangé wrote:
> This thread from a little over a year ago:
>
> http://lists.wpkg.org/pipermail/sheepdog/2019-March/thread.html
>
> states that sheepdog is no longer actively developed. The only mentioned
> users are some companies who are said to have it for legacy reasons with
> plans to replace it by Ceph. There is talk about cutting out existing
> features to turn it into a simple demo of how to write a distributed
> block service. There is no evidence of anyone working on that idea:
>
> https://github.com/sheepdog/sheepdog/commits/master
>
> No real commits to git since Jan 2018, and before then just some minor
> technical debt cleanup..
>
> There is essentially no activity on the mailing list aside from
> patches to QEMU that get CC'd due to our MAINTAINERS entry.
>
> Fedora packages for sheepdog failed to build from upstream source
> because of the more strict linker that no longer merges duplicate
> global symbols. Fedora patches it to add the missing "extern"
> annotations and presumably other distros do to, but upstream source
> remains broken.
>
> There is only basic compile testing, no functional testing of the
> driver.
>
> Since there are no build pre-requisites the sheepdog driver is currently
> enabled unconditionally. This would result in configure issuing a
> deprecation warning by default for all users. Thus the configure default
> is changed to disable it, requiring users to pass --enable-sheepdog to
> build the driver.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> block/sheepdog.c | 15 +++++++++++++++
> configure | 5 +++--
> docs/system/deprecated.rst | 9 +++++++++
> 3 files changed, 27 insertions(+), 2 deletions(-)
>
> diff --git a/block/sheepdog.c b/block/sheepdog.c
> index cbbebc1aaf..7f68bd6a1a 100644
> --- a/block/sheepdog.c
> +++ b/block/sheepdog.c
> @@ -242,6 +242,17 @@ typedef struct SheepdogInode {
> */
> #define FNV1A_64_INIT ((uint64_t)0xcbf29ce484222325ULL)
>
> +static void deprecation_warning(void)
> +{
> + static bool warned = false;
Checkpatch warns there is no need to initialize static bool to false,
otherwise:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> +
> + if (!warned) {
> + warn_report("the sheepdog block driver is deprecated and will be "
> + "removed in a future release");
> + warned = true;
> + }
> +}
[...]
next prev parent reply other threads:[~2020-09-23 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 16:16 [PATCH v2 0/2] block: deprecate the sheepdog driver Daniel P. Berrangé
2020-09-22 16:16 ` [PATCH v2 1/2] block: drop moderated sheepdog mailing list from MAINTAINERS file Daniel P. Berrangé
2020-09-22 17:27 ` Thomas Huth
2020-09-22 17:46 ` Vladimir Sementsov-Ogievskiy
2020-09-22 16:16 ` [PATCH v2 2/2] block: deprecate the sheepdog block driver Daniel P. Berrangé
2020-09-22 17:32 ` Thomas Huth
2020-09-22 17:53 ` Vladimir Sementsov-Ogievskiy
2020-09-23 10:25 ` Philippe Mathieu-Daudé [this message]
2020-09-23 13:50 ` Markus Armbruster
2020-09-22 17:09 ` [PATCH v2 0/2] block: deprecate the sheepdog driver Neal Gompa
2020-09-22 17:42 ` Daniel P. Berrangé
2020-09-22 18:11 ` Neal Gompa
2020-09-23 4:52 ` Vladimir Sementsov-Ogievskiy
2020-09-23 8:24 ` Peter Krempa
2020-09-22 21:10 ` no-reply
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=1d391aab-db3d-a134-9657-d81c7c2d9130@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@redhat.com \
--cc=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.org \
--cc=thuth@redhat.com \
/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).