cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] tunegfs2: Fix label/locktable setting code
Date: Fri, 22 Jul 2011 09:34:08 +0100	[thread overview]
Message-ID: <1311323648.2804.4.camel@menhir> (raw)
In-Reply-To: <4E2806D9.3000403@redhat.com>

Hi,

On Thu, 2011-07-21 at 12:00 +0100, Andrew Price wrote:
> Hi Steve,
> 
> On 20/07/11 10:57, Steven Whitehouse wrote:
> >
> > This is an updated version of the previously posted patch aimed at
> > fixing bz #719135
> 
> Looks good to me. Just a couple of minor notes on input validation...
> 
> With this patch it's possible to set the locktable to ":" using:
> 
> # tunegfs2 -o lockproto=lock_dlm /dev/dm-3
> # tunegfs2 -L : /dev/dm-3
> 
> And although this rightly fails:
> 
> # tunegfs2 -o lockproto=lock_dlm,locktable=foo /dev/dm-3
> locktable error: mising colon in the locktable
> 
> it is still possible to specify a colon-less locktable name with lock_dlm:
> 
> # tunegfs2 -o lockproto=lock_nolock /dev/dm-3
> # tunegfs2 -L foo /dev/dm-3
> # tunegfs2 -o lockproto=lock_dlm /dev/dm-3
> 
Yes, I'm not overly worried by that. Mounting will fail so it is still
impossible to cause a problem by doing that, I think,

Steve.




  reply	other threads:[~2011-07-22  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  9:57 [Cluster-devel] tunegfs2: Fix label/locktable setting code Steven Whitehouse
2011-07-21 11:00 ` Andrew Price
2011-07-22  8:34   ` Steven Whitehouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-07-14 14:20 Steven Whitehouse

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=1311323648.2804.4.camel@menhir \
    --to=swhiteho@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).