From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/2] network/ipsec: Add trap to INT and require root
Date: Mon, 11 Dec 2017 13:23:17 +0100 [thread overview]
Message-ID: <20171211122317.GA7605@rei> (raw)
In-Reply-To: <20171207121819.rojckr2gxgwng2aj@dell5510>
Hi!
> > > +trap "tst_brkm TBROK 'test interrupted'" INT
>
> > Could we add it to test_net.sh?
> Sure. I was even thinking about giving it into test_net.sh and test.sh (i.e. making it the
> default settings), but that's maybe too aggressive.
Unless we find a test that traps INT in order to attempt to cleanup
doing tst_brkm on INT in test library is IMHO okay.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-12-11 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 14:42 [LTP] [RFC PATCH 1/2] network/ipsec: Add trap to INT and require root Petr Vorel
2017-12-06 14:42 ` [LTP] [RFC PATCH 2/2] lib/test_net.sh: Check for ip command Petr Vorel
2017-12-07 11:52 ` Alexey Kodanev
2017-12-07 11:25 ` [LTP] [RFC PATCH 1/2] network/ipsec: Add trap to INT and require root Alexey Kodanev
2017-12-07 12:18 ` Petr Vorel
2017-12-11 12:23 ` Cyril Hrubis [this message]
2017-12-11 14:36 ` 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=20171211122317.GA7605@rei \
--to=chrubis@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox