From: Florian Westphal <fw@strlen.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Florian Westphal <fw@strlen.de>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>, Shuah Khan <shuah@kernel.org>,
pablo@netfilter.org, jeffrin@rajagiritech.edu.in,
horms@verge.net.au, yanhaishuang@cmss.chinamobile.com,
lkft-triage@lists.linaro.org
Subject: Re: selftests:netfilter: nft_nat.sh: internal00-0 Error Could not open file \"-\" No such file or directory
Date: Wed, 27 Nov 2019 23:05:25 +0100 [thread overview]
Message-ID: <20191127220525.GH795@breakpoint.cc> (raw)
In-Reply-To: <CA+G9fYur6RHnz2nzy9RwZ64yUDv0bRs4eP9odLud0mDP9SAA-w@mail.gmail.com>
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> On Tue, 26 Nov 2019 at 21:26, Florian Westphal <fw@strlen.de> wrote:
> >
> > Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> > > Do you see the following error while running selftests netfilter
> > > nft_nat.sh test ?
> > > Are we missing any kernel config fragments ? We are merging configs
> > > from the directory.
> > >
> > > # selftests netfilter nft_nat.sh
> > > netfilter: nft_nat.sh_ #
> > > # Cannot create namespace file \"/var/run/netns/ns1\" File exists
> >
> > 'ns1' is not a good name.
> > What is the output of nft --version?
>
> nftables v0.7 (Scrooge McDuck)
Oh, that explains it. "-" only works
since 0.8.4 ...
I will submit another patch that uses /dev/stdin instead.
prev parent reply other threads:[~2019-11-27 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 3:55 selftests:netfilter: nft_nat.sh: internal00-0 Error Could not open file \"-\" No such file or directory Naresh Kamboju
2019-11-26 15:56 ` Florian Westphal
[not found] ` <20191127001931.GA3717@debian>
2019-11-27 12:45 ` Jeffrin Thalakkottoor
2019-11-27 12:48 ` Jeffrin Thalakkottoor
2019-11-27 19:19 ` Naresh Kamboju
2019-11-27 22:05 ` Florian Westphal [this message]
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=20191127220525.GH795@breakpoint.cc \
--to=fw@strlen.de \
--cc=horms@verge.net.au \
--cc=jeffrin@rajagiritech.edu.in \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=shuah@kernel.org \
--cc=yanhaishuang@cmss.chinamobile.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).