All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 1/2] net: Add tst_net_run helper
Date: Mon, 19 Nov 2018 16:40:04 +0100	[thread overview]
Message-ID: <20181119154004.GB26645@dell5510> (raw)
In-Reply-To: <37a6f27b-096e-8701-b8ee-4132d10ef889@oracle.com>

Hi Alexey,

> >>> Maybe we could signal where error occurred:
> >>> * return 0: ok on both lhost and rhost
> >>> * return 1: failure on lhost
> >>> * return 2: failure on rhost
> >>> * return 3: failure on both lhost and rhost


> >> It is only when there is no "safe" option, right?
> > yes, as safe exit with TCONF and warning.

> >> when doing cleanup?
> > IMHO in any "non-safe" run.

> >> Could we print TWARN message inside tst_net_run() in such case?
> > I wanted tst_net_run() to behave similarly as tst_rhost_run(), which doesn't
> > warn about it. So I propose to add warning to both functions, but also add -q
> > flag (quiet), which suppress this warning.

> I think we don't need it for tst_rhost_run() as it is clear where the
> error has happened. Unlike tst_net_run() without safe option.
OK, make sense, I'll put it just into tst_net_run().


> > The reason for quiet mode is, that (I suppose) there are cases when some
> > features is tested and TWARN isn't wanted. Some examples (looks -s is used often
> > in cleanup functions):

> '-s' is used often in cleanup with tst_rhost_run()?
Sorry, I was wrong. Previously I meant tst_rhost_run *without -s* option.

tst_rhost_run with -s option in cleanup is only in 2 files:
testcases/network/mpls/mpls_lib.sh
testcases/network/tcp_cmds/sendfile/sendfile01
Maybe that's a mistake (unlike C functions where error in SAFE_* continue with
warning, in shell it exits during cleanup).

Without -s we don't get any warning, which is often desirable.
=> I'll put warning and -q switch to suppress it only into tst_net_run().


Kind regards,
Petr

  reply	other threads:[~2018-11-19 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 16:30 [LTP] [PATCH v4 1/2] net: Add tst_net_run helper Petr Vorel
2018-11-13 16:30 ` [LTP] [PATCH v4 2/2] net/ipsec: Add check for xfrm_user kernel module Petr Vorel
2018-11-16 11:51 ` [LTP] [PATCH v4 1/2] net: Add tst_net_run helper Alexey Kodanev
2018-11-16 14:24   ` Petr Vorel
2018-11-19 10:44     ` Alexey Kodanev
2018-11-19 15:40       ` Petr Vorel [this message]
2018-11-19 17:19         ` Alexey Kodanev
2018-11-19 17:38           ` Petr Vorel

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=20181119154004.GB26645@dell5510 \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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.