lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sat, 25 May 2024 04:32:03 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Philip Li <philip.li@...el.com>
Cc: kernel test robot <lkp@...el.com>, 
	Suren Baghdasaryan <surenb@...gle.com>, oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org, 
	Andrew Morton <akpm@...ux-foundation.org>, Linux Memory Management List <linux-mm@...ck.org>
Subject: Re: include/asm-generic/percpu.h:31:40: error: implicit declaration
 of function 'raw_smp_processor_id'

On Sat, May 25, 2024 at 04:08:28PM +0800, Philip Li wrote:
> On Fri, May 24, 2024 at 11:58:30AM -0400, Kent Overstreet wrote:
> > On Tue, May 21, 2024 at 12:31:18AM +0800, kernel test robot wrote:
> > > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > > head:   eb6a9339efeb6f3d2b5c86fdf2382cdc293eca2c
> > > commit: 24e44cc22aa3112082f2ee23137d048c73ca96d5 mm: percpu: enable per-cpu allocation tagging
> > > date:   4 weeks ago
> > > config: mips-randconfig-r133-20240520 (https://download.01.org/0day-ci/archive/20240521/202405210052.DIrMXJNz-lkp@intel.com/config)
> > > compiler: mips-linux-gcc (GCC) 13.2.0
> > > reproduce: (https://download.01.org/0day-ci/archive/20240521/202405210052.DIrMXJNz-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@...el.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202405210052.DIrMXJNz-lkp@intel.com/
> > 
> > I have a fix I'm testing for this but it's going to need a lot of
> > randconfig build testing on all archs.
> > 
> > Philip, could 0day help out with that? I don't know how you schedule
> 
> Got it, we will cover this branch with randconfig build tests.
> 
> > which branches for which testing, and previously the memory allocation
> > profiling didn't get enough build testing before Andrew merged it.
> 
> Sorry about this, we really need extend the test number to generate
> more randconfigs.

It was getting caught by 0day in Andrew's tree, I think it may have just
been a timing thing. This is (one of the reasons) why I'm hoping to get
you a dashboard (and maybe get some test infrastructure consolidation
going, too) - right now I just have no way of knowing how long the
randconfig tests take or when they're finished.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ