From: Wols Lists <antlists@youngman.org.uk>
To: Goldwyn Rodrigues <rgoldwyn@suse.de>, NeilBrown <neilb@suse.com>,
Guoqing Jiang <gqJiang@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 3/3] Safeguard against writing to an active device of another node
Date: Sat, 01 Aug 2015 16:50:23 +0100 [thread overview]
Message-ID: <55BCEABF.6060505@youngman.org.uk> (raw)
In-Reply-To: <55B96474.6080604@suse.de>
On 30/07/15 00:40, Goldwyn Rodrigues wrote:
>>
>> I was wondering if we could make it a run-time dependency though .. a
>> bit like get_cluster_name. We can still do that later I guess. I'm
>> not really sure what is best at the moment.
>>
>
>
> Yes, I would second that: Making these functions a run-time dependency.
> We should have the ability for it to work by just installing libdlm
> (with the proper flags set), rather than recompiling the package for
> cluster features.
Or - maybe unlikely but maybe not - what happens if somebody installs a
binary that was built on a system WITH dlm, but is meant to run on a
system WITHOUT dlm?
Actually, wouldn't that be the typical case for a typical distro?
Cheers,
Wol
next prev parent reply other threads:[~2015-08-01 15:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 8:52 [PATCH 1/3] mdadm: fix wrong condition for go to abort Guoqing Jiang
2015-07-06 8:52 ` [PATCH 2/3] md-cluster: use %-64s to print cluster_name Guoqing Jiang
2015-07-06 8:52 ` [PATCH 3/3] Safeguard against writing to an active device of another node Guoqing Jiang
2015-07-29 7:28 ` NeilBrown
2015-07-29 10:41 ` Guoqing Jiang
2015-07-29 22:02 ` NeilBrown
2015-07-29 23:40 ` Goldwyn Rodrigues
2015-07-30 3:18 ` Guoqing Jiang
2015-08-01 15:50 ` Wols Lists [this message]
2015-08-01 15:54 ` Goldwyn Rodrigues
2015-07-30 3:16 ` Guoqing Jiang
2015-07-30 8:22 ` Guoqing Jiang
2015-07-30 8:38 ` Guoqing Jiang
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=55BCEABF.6060505@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gqJiang@suse.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.com \
--cc=rgoldwyn@suse.de \
/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.