All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Gary Guo <gary@garyguo.net>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: kernel/locking/lockdep.c:727:21: error: 'CONFIG_RUST' undeclared; did you mean 'CONFIG_USB'?
Date: Sat, 04 Jul 2026 04:34:41 +0200	[thread overview]
Message-ID: <202607040403.yLeH4bDF-lkp@intel.com> (raw)

tree:   https://github.com/intel-lab-lkp/linux/commits/Gary-Guo/rust-sync-introduce-a-way-to-create-lock-class-from-caller/20260703-220743
head:   090a8fd3c5e7c50a1ebd6fc2ef51e1dbaaa81378
commit: 090a8fd3c5e7c50a1ebd6fc2ef51e1dbaaa81378 lockdep: delegate Rust lock class printing to Rust code
date:   12 hours ago
config: x86_64-rhel-9.4-kselftests (https://download.01.org/0day-ci/archive/20260704/202607040403.yLeH4bDF-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260704/202607040403.yLeH4bDF-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/202607040403.yLeH4bDF-lkp@intel.com/

All errors (new ones prefixed by >>):

   kernel/locking/lockdep.c: In function '__print_lock_name':
>> kernel/locking/lockdep.c:727:21: error: 'CONFIG_RUST' undeclared (first use in this function); did you mean 'CONFIG_USB'?
     727 |                 if (CONFIG_RUST && class->name == lockdep_rust_name)
         |                     ^~~~~~~~~~~
         |                     CONFIG_USB
   kernel/locking/lockdep.c:727:21: note: each undeclared identifier is reported only once for each function it appears in


vim +727 kernel/locking/lockdep.c

   716	
   717	static void __print_lock_name(struct held_lock *hlock, struct lock_class *class)
   718	{
   719		char str[KSYM_NAME_LEN];
   720		const char *name;
   721	
   722		name = class->name;
   723		if (!name) {
   724			name = __get_key_name(class->key, str);
   725			printk(KERN_CONT "%s", name);
   726		} else {
 > 727			if (CONFIG_RUST && class->name == lockdep_rust_name)
   728				lockdep_print_rust_name((struct lock_class_key *)(
   729					class->key - class->subclass
   730				));
   731			else
   732				printk(KERN_CONT "%s", name);
   733			if (class->name_version > 1)
   734				printk(KERN_CONT "#%d", class->name_version);
   735			if (class->subclass)
   736				printk(KERN_CONT "/%d", class->subclass);
   737			if (hlock && class->print_fn)
   738				class->print_fn(hlock->instance);
   739		}
   740	}
   741	

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

                 reply	other threads:[~2026-07-04  2:35 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=202607040403.yLeH4bDF-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=gary@garyguo.net \
    --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.