Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Liu Yiding <liuyd.fnst@cn.fujitsu.com>
To: Florian Westphal <fw@strlen.de>
Cc: <linux-kselftest@vger.kernel.org>,
	Philip Li <philip.li@intel.com>,
	Stefano Brivio <sbrivio@redhat.com>
Subject: Re: About selftests/netfilter failed subtests
Date: Mon, 27 Apr 2020 08:40:19 +0800	[thread overview]
Message-ID: <3646ad42-8b80-eff2-cedc-e04dbaa983c6@cn.fujitsu.com> (raw)
In-Reply-To: <20200426074529.GG32392@breakpoint.cc>

Very appericate it !

On 4/26/20 3:45 PM, Florian Westphal wrote:
> Liu Yiding <liuyd.fnst@cn.fujitsu.com> wrote:
>> Hi, all.
>>
>> Our team works on testing kernel commit and reporting regression.
>>
>> Tool selftests is important to us.
>>
>> Recently i enabled netfilter in out testing env, i met below failed
>> subtests.
>>
>> ```
>>
>>    "kernel-selftests.netfilter.nft_nat.sh.fail": [
>> "kernel-selftests.netfilter.conntrack_icmp_related.sh.fail": [
>>    "kernel-selftests.netfilter.nft_flowtable.sh.fail": [
>>    "kernel-selftests.netfilter.nft_concat_range.sh.fail": [
>>
>> ```
>>
>> Our testing env:
>>
>>
>> It looks that i missed some modules or i get wrong config of nftables. I had
>> opend kconfig mentioned in netfilter/config.
> Maybe its incomplete. From a quick glance, all of these should be on:
>
> # CONFIG_NFT_OBJREF is not set
> # CONFIG_NFT_NAT is not set
> # CONFIG_NF_FLOW_TABLE is not set
> # CONFIG_NF_TABLES_NETDEV is not set
>
>
>
-- 
Best Regards.
Liu Yiding




      reply	other threads:[~2020-04-27  0:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4aa34cdf-2145-01e7-acdf-2fc5d931bbee@cn.fujitsu.com>
2020-04-26  7:45 ` About selftests/netfilter failed subtests Florian Westphal
2020-04-27  0:40   ` Liu Yiding [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=3646ad42-8b80-eff2-cedc-e04dbaa983c6@cn.fujitsu.com \
    --to=liuyd.fnst@cn.fujitsu.com \
    --cc=fw@strlen.de \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=philip.li@intel.com \
    --cc=sbrivio@redhat.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