From: Stefano Garzarella <sgarzare@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-trivial@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>,
Jason Wang <jasowang@redhat.com>,
qemu-devel@nongnu.org,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [Qemu-devel] [PATCH] net/slirp: fix the error message when the prefix len is invalid
Date: Thu, 9 May 2019 17:16:36 +0200 [thread overview]
Message-ID: <20190509151636.xcon4rt7ybdo32pz@steredhat> (raw)
In-Reply-To: <87y33f1xw4.fsf@dusky.pond.sub.org>
On Thu, May 09, 2019 at 04:54:35PM +0200, Markus Armbruster wrote:
> Stefano Garzarella <sgarzare@redhat.com> writes:
>
> > Add a missing parentheses at the end of the error message,
> > when we have an invalid prefix len.
> >
> > Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
> > ---
> > net/slirp.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/net/slirp.c b/net/slirp.c
> > index 95934fb36d..0f4ae0abc0 100644
> > --- a/net/slirp.c
> > +++ b/net/slirp.c
> > @@ -498,7 +498,8 @@ static int net_slirp_init(NetClientState *peer, const char *model,
> > }
> > if (vprefix6_len < 0 || vprefix6_len > 126) {
> > error_setg(errp,
> > - "Invalid prefix provided (prefix len must be in range 0-126");
> > + "Invalid prefix provided "
> > + "(prefix len must be in range 0-126)");
> > return -1;
> > }
>
> Preexisting: the error message fails to identify the offending
> parameter. The user needs to make the connection to "ipv6-prefixlen"
> based on the fact that the only parameters with "prefix" in name or
> description are "ipv6-prefix" and "ipv6-prefixlen", and only the latter
> is a length.
>
> What about "Parameter 'ipv6-prefixlen' expects a length below 127", or
> "Parameter 'ipv6-prefixlen' expects a value between 0 and 126"?
"Parameter 'ipv6-prefixlen' expects a value between 0 and 126" should be
fine.
Otherwise, since other errors didn't refer to the parameter name, we can
simply add IPv6 in this way:
"Invalid IPv6 prefix provided (IPv6 prefix len must be between 0 and 126)"
But I'm fine also with your proposal.
Thanks,
Stefano
next prev parent reply other threads:[~2019-05-09 15:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 13:37 [Qemu-devel] [PATCH] net/slirp: fix the error message when the prefix len is invalid Stefano Garzarella
2019-05-09 13:54 ` Marc-André Lureau
2019-05-09 14:54 ` Markus Armbruster
2019-05-09 15:16 ` Stefano Garzarella [this message]
2019-05-10 5:56 ` Markus Armbruster
2019-05-10 7:58 ` Stefano Garzarella
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=20190509151636.xcon4rt7ybdo32pz@steredhat \
--to=sgarzare@redhat.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=samuel.thibault@ens-lyon.org \
/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).