public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Rohit Maheshwari <rohitm@chelsio.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/crypto/chelsio/chcr_ktls.c:1018: undefined reference to `tls_validate_xmit_skb'
Date: Fri, 29 May 2020 00:36:44 +0800	[thread overview]
Message-ID: <202005290043.ltImAHT0%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1937 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   b0c3ba31be3e45a130e13b278cf3b90f69bda6f6
commit: 5a4b9fe7fece62ecab6fb28fe92362f83b41c33e cxgb4/chcr: complete record tx handling
date:   3 months ago
config: i386-randconfig-a013-20200528 (attached as .config)
compiler: gcc-5 (Ubuntu 5.5.0-12ubuntu1) 5.5.0 20171010
reproduce (this is a W=1 build):
        git checkout 5a4b9fe7fece62ecab6fb28fe92362f83b41c33e
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>, old ones prefixed by <<):

ld: drivers/crypto/chelsio/chcr_ktls.o: in function `chcr_ktls_xmit':
>> drivers/crypto/chelsio/chcr_ktls.c:1018: undefined reference to `tls_validate_xmit_skb'
ld: drivers/crypto/chelsio/chcr_ktls.c:1078: undefined reference to `tls_get_record'

vim +1018 drivers/crypto/chelsio/chcr_ktls.c

   996	
   997	/* nic tls TX handler */
   998	int chcr_ktls_xmit(struct sk_buff *skb, struct net_device *dev)
   999	{
  1000		struct chcr_ktls_ofld_ctx_tx *tx_ctx;
  1001		struct tcphdr *th = tcp_hdr(skb);
  1002		int data_len, qidx, ret = 0, mss;
  1003		struct tls_record_info *record;
  1004		struct chcr_ktls_info *tx_info;
  1005		u32 tls_end_offset, tcp_seq;
  1006		struct tls_context *tls_ctx;
  1007		struct sk_buff *local_skb;
  1008		int new_connection_state;
  1009		struct sge_eth_txq *q;
  1010		struct adapter *adap;
  1011		unsigned long flags;
  1012	
  1013		tcp_seq = ntohl(th->seq);
  1014	
  1015		mss = skb_is_gso(skb) ? skb_shinfo(skb)->gso_size : skb->data_len;
  1016	
  1017		/* check if we haven't set it for ktls offload */
> 1018		if (!skb->sk || !tls_is_sk_tx_device_offloaded(skb->sk))

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39524 bytes --]

                 reply	other threads:[~2020-05-28 16:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202005290043.ltImAHT0%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rohitm@chelsio.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