From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:afs-testing 35/35] net/rxrpc/rxperf.c:587:undefined reference to `crypto_krb5_find_enctype'
Date: Mon, 10 Feb 2025 12:44:03 +0800 [thread overview]
Message-ID: <202502101229.Cm30u9yV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git afs-testing
head: 6385ba8f265471ebf57f38e2bd2e6a4fabac7424
commit: 6385ba8f265471ebf57f38e2bd2e6a4fabac7424 [35/35] rxrpc: rxperf: Add test RxGK server keys
config: csky-randconfig-002-20250210 (https://download.01.org/0day-ci/archive/20250210/202502101229.Cm30u9yV-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250210/202502101229.Cm30u9yV-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/202502101229.Cm30u9yV-lkp@intel.com/
All errors (new ones prefixed by >>):
csky-linux-ld: net/rxrpc/rxperf.o: in function `rxperf_add_yfs_rxgk_key':
>> net/rxrpc/rxperf.c:587:(.text.unlikely+0x16): undefined reference to `crypto_krb5_find_enctype'
>> csky-linux-ld: net/rxrpc/rxperf.c:619:(.text.unlikely+0xb4): undefined reference to `crypto_krb5_find_enctype'
net/ipv4/tcp_ipv4.o: in function `tcp_add_backlog':
net/ipv4/tcp_ipv4.c:2028:(.text+0x2838): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.c:2063:(.text+0x297a): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.c:2076:(.text+0x29e4): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.c:2106:(.text+0x2ab6): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.c:2108:(.text+0x2ad2): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.o: in function `tcp_checksum_complete':
include/net/tcp.h:1484:(.text+0x2ae2): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.o: in function `spin_unlock':
include/linux/spinlock.h:391:(.text+0x2aee): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.o: in function `tcp_add_backlog':
net/ipv4/tcp_ipv4.c:2009:(.text+0x2822): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.c:2106:(.text+0x2ab2): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
net/ipv4/tcp_ipv4.c:2106:(.text+0x2aba): relocation truncated to fit: R_CKCORE_PCREL_IMM16BY4 against `__jump_table'
vim +587 net/rxrpc/rxperf.c
581
582 /*
583 * Add a yfs-rxgk key to the security keyring.
584 */
585 static int rxperf_add_yfs_rxgk_key(struct key *keyring, u32 enctype)
586 {
> 587 const struct krb5_enctype *krb5 = crypto_krb5_find_enctype(enctype);
588 key_ref_t kref;
589 char name[64];
590 int ret;
591 u8 key[32];
592
593 if (!krb5 || krb5->key_len > sizeof(key))
594 return 0;
595
596 /* The key is just { 0, 1, 2, 3, 4, ... } */
597 for (int i = 0; i < krb5->key_len; i++)
598 key[i] = i;
599
600 sprintf(name, "%u:6:1:%u", RX_PERF_SERVICE, enctype);
601
602 kref = key_create_or_update(make_key_ref(keyring, true),
603 "rxrpc_s", name,
604 key, krb5->key_len,
605 KEY_POS_VIEW | KEY_POS_READ | KEY_POS_SEARCH |
606 KEY_USR_VIEW,
607 KEY_ALLOC_NOT_IN_QUOTA);
608
609 if (IS_ERR(kref)) {
610 pr_err("Can't allocate rxperf server key: %ld\n", PTR_ERR(kref));
611 return PTR_ERR(kref);
612 }
613
614 ret = key_link(keyring, key_ref_to_ptr(kref));
615 if (ret < 0)
616 pr_err("Can't link rxperf server key: %d\n", ret);
617 key_ref_put(kref);
618 return ret;
> 619 }
620
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-10 4:44 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=202502101229.Cm30u9yV-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.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 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.