From: kernel test robot <lkp@intel.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com, borisp@nvidia.com,
john.fastabend@gmail.com, maximmi@nvidia.com, tariqt@nvidia.com,
vfedorenko@novek.ru, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next 7/7] tls: rx: do not use the standard strparser
Date: Tue, 19 Jul 2022 10:40:18 +0800 [thread overview]
Message-ID: <202207191049.lGxYs81r-lkp@intel.com> (raw)
In-Reply-To: <20220718194811.1728061-8-kuba@kernel.org>
Hi Jakub,
I love your patch! Perhaps something to improve:
[auto build test WARNING on net-next/master]
url: https://github.com/intel-lab-lkp/linux/commits/Jakub-Kicinski/tls-rx-decrypt-from-the-TCP-queue/20220719-035116
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 6e693a104207fbf5a22795c987e8964c0a1ffe2d
config: x86_64-rhel-8.3-syz (https://download.01.org/0day-ci/archive/20220719/202207191049.lGxYs81r-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/2a6e8eea293987aa4507bf82c5952f49752c9be3
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Jakub-Kicinski/tls-rx-decrypt-from-the-TCP-queue/20220719-035116
git checkout 2a6e8eea293987aa4507bf82c5952f49752c9be3
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>, old ones prefixed by <<):
>> WARNING: modpost: net/tls/tls.o(.init.text+0x65): Section mismatch in reference from the function init_module() to the function .exit.text:tls_device_cleanup()
The function __init init_module() references
a function __exit tls_device_cleanup().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
tls_device_cleanup() so it may be used outside an exit section.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-07-19 2:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 19:48 [PATCH net-next 0/7] tls: rx: decrypt from the TCP queue Jakub Kicinski
2022-07-18 19:48 ` [PATCH net-next 1/7] tls: rx: wrap recv_pkt accesses in helpers Jakub Kicinski
2022-07-18 19:48 ` [PATCH net-next 2/7] tls: rx: factor SW handling out of tls_rx_one_record() Jakub Kicinski
2022-07-18 19:48 ` [PATCH net-next 3/7] tls: rx: don't free the output in case of zero-copy Jakub Kicinski
2022-07-18 19:48 ` [PATCH net-next 4/7] tls: rx: device: keep the zero copy status with offload Jakub Kicinski
2022-07-18 19:48 ` [PATCH net-next 5/7] tcp: allow tls to decrypt directly from the tcp rcv queue Jakub Kicinski
2022-07-18 19:48 ` [PATCH net-next 6/7] tls: rx: device: add input CoW helper Jakub Kicinski
2022-07-18 19:48 ` [PATCH net-next 7/7] tls: rx: do not use the standard strparser Jakub Kicinski
2022-07-19 2:40 ` kernel test robot [this message]
2022-07-19 13:01 ` 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=202207191049.lGxYs81r-lkp@intel.com \
--to=lkp@intel.com \
--cc=borisp@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=maximmi@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.com \
--cc=vfedorenko@novek.ru \
/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.