All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:crypto-krb5 22/27] fs/afs/cm_security.c:48:undefined reference to `rxkad_kernel_respond_to_challenge'
Date: Mon, 10 Feb 2025 14:40:10 +0800	[thread overview]
Message-ID: <202502101452.83heiFcl-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git crypto-krb5
head:   eb2ef20c8f90912443f70e3cc46ddd4d4dea591f
commit: 6aad41326de842cc9aa4cd58fe8fb4018a5c3241 [22/27] rxrpc: Allow CHALLENGEs to the passed to the app for a RESPONSE
config: sparc-randconfig-002-20250210 (https://download.01.org/0day-ci/archive/20250210/202502101452.83heiFcl-lkp@intel.com/config)
compiler: sparc64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250210/202502101452.83heiFcl-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/202502101452.83heiFcl-lkp@intel.com/

All errors (new ones prefixed by >>):

   sparc64-linux-ld: fs/afs/cm_security.o: in function `afs_respond_to_challenge':
>> fs/afs/cm_security.c:48:(.text+0xbc): undefined reference to `rxkad_kernel_respond_to_challenge'


vim +48 fs/afs/cm_security.c

    14	
    15	/*
    16	 * Respond to an RxGK challenge, adding appdata.
    17	 */
    18	static int afs_respond_to_challenge(struct sk_buff *challenge)
    19	{
    20		struct rxrpc_peer *peer;
    21		unsigned long peer_data;
    22		u16 service_id;
    23		u8 security_index;
    24	
    25		rxrpc_kernel_query_challenge(challenge, &peer, &peer_data,
    26					     &service_id, &security_index);
    27	
    28		_enter("%u,%u", service_id, security_index);
    29	
    30		switch (service_id) {
    31			/* We don't send CM_SERVICE RPCs, so don't expect a challenge
    32			 * therefrom.
    33			 */
    34		case FS_SERVICE:
    35		case VL_SERVICE:
    36		case YFS_FS_SERVICE:
    37		case YFS_VL_SERVICE:
    38			break;
    39		default:
    40			pr_warn("Can't respond to unknown challenge %u:%u",
    41				service_id, security_index);
    42			return rxrpc_kernel_reject_challenge(challenge, RX_USER_ABORT, -EPROTO,
    43							     afs_abort_unsupported_sec_class);
    44		}
    45	
    46		switch (security_index) {
    47		case RXRPC_SECURITY_RXKAD:
  > 48			return rxkad_kernel_respond_to_challenge(challenge);
    49	
    50		default:
    51			return rxrpc_kernel_reject_challenge(challenge, RX_USER_ABORT, -EPROTO,
    52							     afs_abort_unsupported_sec_class);
    53		}
    54	}
    55	

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

                 reply	other threads:[~2025-02-10  6:40 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=202502101452.83heiFcl-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.