public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Xu" <dxu@dxuuu.xyz>
To: "kernel test robot" <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	"Alexei Starovoitov" <ast@kernel.org>
Subject: Re: progs/test_bpf_nf_fail.c:82:4: error: incomplete definition of type 'struct nf_conn'
Date: Wed, 14 Dec 2022 16:47:49 -0700	[thread overview]
Message-ID: <263e2fc0-9833-4bef-84e3-902fb3a8dbad@app.fastmail.com> (raw)
In-Reply-To: <202212121614.1CSzW0Xw-lkp@intel.com>

On Mon, Dec 12, 2022, at 1:57 AM, kernel test robot wrote:
> Hi Daniel,
>
> First bad commit (maybe != root cause):
>
> tree:   
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> master
> head:   830b3c68c1fb1e9176028d02ef86f3cf76aa2476
> commit: e2d75e954c0a277b8fa0ddf666ddd4f9b73195f7 selftests/bpf: Add 
> tests for writing to nf_conn:mark
> date:   3 months ago
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce:
>         # 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e2d75e954c0a277b8fa0ddf666ddd4f9b73195f7
>         git remote add linus 
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>         git fetch --no-tags linus master
>         git checkout e2d75e954c0a277b8fa0ddf666ddd4f9b73195f7
>         make O=/tmp/kselftest headers
>         make O=/tmp/kselftest -C tools/testing/selftests
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
>>> progs/test_bpf_nf_fail.c:82:4: error: incomplete definition of type 'struct nf_conn'
>            ct->status = 0xF00;
>            ~~^
>    progs/test_bpf_nf_fail.c:7:8: note: forward declaration of 'struct nf_conn'
>    struct nf_conn;
>           ^
>    1 error generated.
>
> -- 
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
> Attachments:
> * config

Not sure what to do about this. Seems like we'd want conditional compilation
for selftests depending on build config. But maybe effort not worth it since
there's a specific CI environment? And unlikely that connmarks disabled on
most distro kernels.

Lemme know if it's worthwhile to fix. Otherwise I will ignore.

Thanks,
Daniel

  reply	other threads:[~2022-12-14 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  8:57 progs/test_bpf_nf_fail.c:82:4: error: incomplete definition of type 'struct nf_conn' kernel test robot
2022-12-14 23:47 ` Daniel Xu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-10-27 18:46 kernel test robot

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=263e2fc0-9833-4bef-84e3-902fb3a8dbad@app.fastmail.com \
    --to=dxu@dxuuu.xyz \
    --cc=ast@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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