qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Wen Congyang <wency@cn.fujitsu.com>
Cc: qemu-block@nongnu.org, Alberto Garcia <berto@igalia.com>,
	qemu-devl <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] quorum: validate vote threshold against num_children even if read-pattern is fifo
Date: Thu, 20 Aug 2015 19:27:47 +0200	[thread overview]
Message-ID: <20150820172747.GB2349@noname.redhat.com> (raw)
In-Reply-To: <55D3EF90.3050702@cn.fujitsu.com>

Am 19.08.2015 um 04:53 hat Wen Congyang geschrieben:
> Ping...

It might have helped to...

a) CC the qemu-block mailing list
b) CC the subsystem maintainer that should apply the patch (according to
   scripts/get_maintainer.pl that's me with Berto's Acked-by)
c) include the "PATCH" keyword in the subject line.

I'm copying qemu-block now and will consider the patch once I'm back
from KVM Forum.

Kevin


> On 07/03/2015 02:45 PM, Wen Congyang wrote:
> > We need to use threshold to check if too many write operation fails.
> > If threshold is larger than num children, we always get write error
> > event even if all write operations success.
> > 
> > Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
> > ---
> >  block/quorum.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> > 
> > diff --git a/block/quorum.c b/block/quorum.c
> > index a7df17c..b0eead0 100644
> > --- a/block/quorum.c
> > +++ b/block/quorum.c
> > @@ -894,6 +894,12 @@ static int quorum_open(BlockDriverState *bs, QDict *options, int flags,
> >      }
> >  
> >      s->threshold = qemu_opt_get_number(opts, QUORUM_OPT_VOTE_THRESHOLD, 0);
> > +    /* and validate it against s->num_children */
> > +    ret = quorum_valid_threshold(s->threshold, s->num_children, &local_err);
> > +    if (ret < 0) {
> > +        goto exit;
> > +    }
> > +
> >      ret = parse_read_pattern(qemu_opt_get(opts, QUORUM_OPT_READ_PATTERN));
> >      if (ret < 0) {
> >          error_setg(&local_err, "Please set read-pattern as fifo or quorum");
> > @@ -902,12 +908,6 @@ static int quorum_open(BlockDriverState *bs, QDict *options, int flags,
> >      s->read_pattern = ret;
> >  
> >      if (s->read_pattern == QUORUM_READ_PATTERN_QUORUM) {
> > -        /* and validate it against s->num_children */
> > -        ret = quorum_valid_threshold(s->threshold, s->num_children, &local_err);
> > -        if (ret < 0) {
> > -            goto exit;
> > -        }
> > -
> >          /* is the driver in blkverify mode */
> >          if (qemu_opt_get_bool(opts, QUORUM_OPT_BLKVERIFY, false) &&
> >              s->num_children == 2 && s->threshold == 2) {
> > 
> 
> 

  reply	other threads:[~2015-08-20 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  6:45 [Qemu-devel] quorum: validate vote threshold against num_children even if read-pattern is fifo Wen Congyang
2015-07-03  8:41 ` Alberto Garcia
2015-07-03  8:50   ` Wen Congyang
2015-08-19  2:53 ` Wen Congyang
2015-08-20 17:27   ` Kevin Wolf [this message]
2015-08-24 18:26 ` Max Reitz
2015-08-26 15:29 ` Max Reitz

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=20150820172747.GB2349@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=berto@igalia.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wency@cn.fujitsu.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).