linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Waiman Long <longman@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Frederic Weisbecker <frederic@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	linux-kernel@vger.kernel.org, Waiman Long <longman@redhat.com>
Subject: Re: [PATCH 2/3] debugobjects: Show the state of debug_objects_enabled
Date: Fri, 6 Jun 2025 06:51:53 +0800	[thread overview]
Message-ID: <202506060634.mQtyT7cN-lkp@intel.com> (raw)
In-Reply-To: <20250604220926.870760-3-longman@redhat.com>

Hi Waiman,

kernel test robot noticed the following build errors:

[auto build test ERROR on tip/timers/core]
[also build test ERROR on akpm-mm/mm-everything tip/core/debugobjects linus/master v6.15 next-20250605]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Waiman-Long/debugobjects-Add-ODEBUG_FLAG_NO_ALLOC-to-disable-memory-allocation/20250605-061211
base:   tip/timers/core
patch link:    https://lore.kernel.org/r/20250604220926.870760-3-longman%40redhat.com
patch subject: [PATCH 2/3] debugobjects: Show the state of debug_objects_enabled
config: arm-randconfig-002-20250606 (https://download.01.org/0day-ci/archive/20250606/202506060634.mQtyT7cN-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250606/202506060634.mQtyT7cN-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/202506060634.mQtyT7cN-lkp@intel.com/

All errors (new ones prefixed by >>):

   lib/debugobjects.c: In function 'check_results':
>> lib/debugobjects.c:1325:17: error: implicit declaration of function 'debug_object_disable'; did you mean 'debug_objects_disable'? [-Werror=implicit-function-declaration]
    1325 |                 debug_object_disable("selftest");
         |                 ^~~~~~~~~~~~~~~~~~~~
         |                 debug_objects_disable
   cc1: some warnings being treated as errors


vim +1325 lib/debugobjects.c

  1288	
  1289	static int __init
  1290	check_results(void *addr, enum debug_obj_state state, int fixups, int warnings)
  1291	{
  1292		struct debug_bucket *db;
  1293		struct debug_obj *obj;
  1294		unsigned long flags;
  1295		int res = -EINVAL;
  1296	
  1297		db = get_bucket((unsigned long) addr);
  1298	
  1299		raw_spin_lock_irqsave(&db->lock, flags);
  1300	
  1301		obj = lookup_object(addr, db);
  1302		if (!obj && state != ODEBUG_STATE_NONE) {
  1303			WARN(1, KERN_ERR "ODEBUG: selftest object not found\n");
  1304			goto out;
  1305		}
  1306		if (obj && obj->state != state) {
  1307			WARN(1, KERN_ERR "ODEBUG: selftest wrong state: %d != %d\n",
  1308			       obj->state, state);
  1309			goto out;
  1310		}
  1311		if (fixups != debug_objects_fixups) {
  1312			WARN(1, KERN_ERR "ODEBUG: selftest fixups failed %d != %d\n",
  1313			       fixups, debug_objects_fixups);
  1314			goto out;
  1315		}
  1316		if (warnings != debug_objects_warnings) {
  1317			WARN(1, KERN_ERR "ODEBUG: selftest warnings failed %d != %d\n",
  1318			       warnings, debug_objects_warnings);
  1319			goto out;
  1320		}
  1321		res = 0;
  1322	out:
  1323		raw_spin_unlock_irqrestore(&db->lock, flags);
  1324		if (res)
> 1325			debug_object_disable("selftest");
  1326		return res;
  1327	}
  1328	

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


           reply	other threads:[~2025-06-05 22:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20250604220926.870760-3-longman@redhat.com>]

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=202506060634.mQtyT7cN-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=anna-maria@linutronix.de \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=longman@redhat.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=tglx@linutronix.de \
    /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