From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 0/3] Clvmd -E fixes
Date: Thu, 22 Sep 2011 18:06:56 +0200 [thread overview]
Message-ID: <4E7B5D20.5060107@redhat.com> (raw)
In-Reply-To: <4E7B5B97.9020703@redhat.com>
Dne 22.9.2011 18:00, Milan Broz napsal(a):
>
> On 09/22/2011 11:52 AM, Zdenek Kabelac wrote:
>> Patchset fixed restart of clvmd with -E option.
>>
>> 1st. Adds support for easier restart of clvmd
>> (i.e. -Isinglenode is preserved).
>>
>> 2nd. Bug fixes support of -E arg.
>
> ack these two.
>
> (maybe cluster lock type is on of the attribute we can store
> in udev db? to read it later :-)
>
>
>> 3rd. Allows to build test suite script for checking clvmd restart.
>> (Any better idea here ?)
>
> We need something for testsuite but I would like to avoid any online
> reconfiguration of daemon paths, this is tricky and bug there is
> security problem (clvms -S must not start arbitrary program
> - it run with root privileges.)
Note - setting (LVM_CLVMD_BINARY as was suggest by agk) must be done before
executing the first clvmd.
You can't influence anything by any further clvmd -S call - since this
environment is not passed to the original restarting daemons.
Thus it should not introduce security risk here - as you are working only with
settings you've had with the first start.
(If someone could manipulate root's environment - he could surely replace disc
content as well)
Zdenek
prev parent reply other threads:[~2011-09-22 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 9:52 [PATCH 0/3] Clvmd -E fixes Zdenek Kabelac
2011-09-22 9:52 ` [PATCH 1/3] Add named cluster_ops Zdenek Kabelac
2011-09-22 9:52 ` [PATCH 2/3] CLVMD bugfix support arg -E Zdenek Kabelac
2011-09-22 9:52 ` [PATCH 3/3] CLVMD support for CLVMD_BINARY and LVM_BINARY Zdenek Kabelac
2011-09-22 16:00 ` [PATCH 0/3] Clvmd -E fixes Milan Broz
2011-09-22 16:06 ` Zdenek Kabelac [this message]
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=4E7B5D20.5060107@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@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 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.