public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] testcases: netns: Handle "Operation not supported" error
Date: Wed, 8 Aug 2018 15:05:12 +0200	[thread overview]
Message-ID: <20180808130512.GD19147@rei> (raw)
In-Reply-To: <1ef13fe5-debb-57ff-422b-b2b5d3460523@oracle.com>

Hi!
> Not sure if the same should be here. The test-cases with IPsec involve
> various crypto drivers that are much easier and better to check with
> ip/netlink, and we also check both: the support in iproute and kernel.
> I guess, veth and dummy virtual drivers could be checked with:
>   
>    modprobe -q veth || tst_brkm TCONF ...

That will possibly break on embedded systems that have everything
compiled-in kernel, not sure if there are any out there.

> Perhaps, we could add tst_drivers_available() helper to the library.

That's a good idea, that way it could be at least tweaked in a single
place.

-- 
Cyril Hrubis
chrubis@suse.cz

  reply	other threads:[~2018-08-08 13:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 14:12 [LTP] [PATCH 1/2] testcases: netns: Check TUN support enabled =?unknown-8bit?q?Myl=C3=A8ne?= Josserand
2018-08-02 14:12 ` [LTP] [PATCH 2/2] testcases: netns: Handle "Operation not supported" error =?unknown-8bit?q?Myl=C3=A8ne?= Josserand
2018-08-08 11:16   ` Alexey Kodanev
2018-08-08 13:05     ` Cyril Hrubis [this message]
2018-08-08 13:31       ` Thomas Petazzoni
2018-08-08 14:06         ` Cyril Hrubis
2018-08-08 13:53       ` Alexey Kodanev
2018-08-08 14:08         ` Cyril Hrubis
2018-10-04 13:06   ` Petr Vorel
2018-10-08  9:28     ` =?unknown-8bit?q?Myl=C3=A8ne?= Josserand
2018-10-08 10:15       ` Petr Vorel
2018-10-04 12:59 ` [LTP] [PATCH 1/2] testcases: netns: Check TUN support enabled 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=20180808130512.GD19147@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