All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Vadim Fedorenko <vadfed@meta.com>,
	Vadim Fedorenko <vadim.fedorenko@linux.dev>,
	Jakub Kicinski <kuba@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Andrii Nakryiko <andrii@kernel.org>,
	Alexei Starovoitov <ast@kernel.org>,
	Mykola Lysenko <mykolal@fb.com>,
	Herbert Xu <herbert@gondor.apana.org.au>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v10 1/4] bpf: make common crypto API for TC/XDP programs
Date: Tue, 23 Apr 2024 19:56:10 +0800	[thread overview]
Message-ID: <202404231955.qUkSEasH-lkp@intel.com> (raw)
In-Reply-To: <20240422225024.2847039-2-vadfed@meta.com>

Hi Vadim,

kernel test robot noticed the following build warnings:

[auto build test WARNING on bpf-next/master]

url:    https://github.com/intel-lab-lkp/linux/commits/Vadim-Fedorenko/bpf-make-common-crypto-API-for-TC-XDP-programs/20240423-070416
base:   https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git master
patch link:    https://lore.kernel.org/r/20240422225024.2847039-2-vadfed%40meta.com
patch subject: [PATCH bpf-next v10 1/4] bpf: make common crypto API for TC/XDP programs
config: riscv-defconfig (https://download.01.org/0day-ci/archive/20240423/202404231955.qUkSEasH-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 5ef5eb66fb428aaf61fb51b709f065c069c11242)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240423/202404231955.qUkSEasH-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202404231955.qUkSEasH-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/bpf/crypto.c:34: warning: Function parameter or struct member 'reserved' not described in 'bpf_crypto_params'
   kernel/bpf/crypto.c:55: warning: Function parameter or struct member 'siv_len' not described in 'bpf_crypto_ctx'


vim +34 kernel/bpf/crypto.c

    17	
    18	/* BPF crypto initialization parameters struct */
    19	/**
    20	 * struct bpf_crypto_params - BPF crypto initialization parameters structure
    21	 * @type:	The string of crypto operation type.
    22	 * @algo:	The string of algorithm to initialize.
    23	 * @key:	The cipher key used to init crypto algorithm.
    24	 * @key_len:	The length of cipher key.
    25	 * @authsize:	The length of authentication tag used by algorithm.
    26	 */
    27	struct bpf_crypto_params {
    28		char type[14];
    29		u8 reserved[2];
    30		char algo[128];
    31		u8 key[256];
    32		u32 key_len;
    33		u32 authsize;
  > 34	};
    35	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2024-04-23 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 22:50 [PATCH bpf-next v10 0/4] BPF crypto API framework Vadim Fedorenko
2024-04-22 22:50 ` [PATCH bpf-next v10 1/4] bpf: make common crypto API for TC/XDP programs Vadim Fedorenko
2024-04-23 11:56   ` kernel test robot [this message]
2024-04-24 23:04   ` Martin KaFai Lau
2024-04-22 22:50 ` [PATCH bpf-next v10 2/4] bpf: crypto: add skcipher to bpf crypto Vadim Fedorenko
2024-04-22 22:50 ` [PATCH bpf-next v10 3/4] selftests: bpf: crypto skcipher algo selftests Vadim Fedorenko
2024-04-22 22:50 ` [PATCH bpf-next v10 4/4] selftests: bpf: crypto: add benchmark for crypto functions Vadim Fedorenko
2024-04-24 22:43   ` Martin KaFai Lau
2024-04-24 23:00     ` Vadim Fedorenko
2024-04-24 23:10 ` [PATCH bpf-next v10 0/4] BPF crypto API framework patchwork-bot+netdevbpf

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=202404231955.qUkSEasH-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=vadfed@meta.com \
    --cc=vadim.fedorenko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.