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]
Message-ID: <Zt+V1fRCG+rspXub@rli9-mobl>
Date: Tue, 10 Sep 2024 08:41:57 +0800
From: Philip Li <philip.li@...el.com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: kernel test robot <lkp@...el.com>, <oe-kbuild-all@...ts.linux.dev>,
	<linux-kernel@...r.kernel.org>
Subject: Re: ERROR: start_text address is c000000000000700, should be
 c000000000000200

On Mon, Sep 09, 2024 at 02:13:19PM -0400, Steven Rostedt wrote:
> On Tue, 10 Sep 2024 02:05:29 +0800
> kernel test robot <lkp@...el.com> wrote:
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   da3ea35007d0af457a0afc87e84fddaebc4e0b63
> > commit: 6e2fdceffdc6bd7b8ba314a1d1b976721533c8f9 tracing: Use refcount for trace_event_file reference counter
> > date:   5 weeks ago
> > config: powerpc64-randconfig-003-20240908 (https://download.01.org/0day-ci/archive/20240910/202409100106.A8692079-lkp@intel.com/config)
> > compiler: powerpc64-linux-gcc (GCC) 14.1.0
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240910/202409100106.A8692079-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/202409100106.A8692079-lkp@intel.com/
> > 
> > All errors (new ones prefixed by >>):
> > 
> > >> ERROR: start_text address is c000000000000700, should be c000000000000200  
> >    ERROR: try to enable LD_HEAD_STUB_CATCH config option
> >    ERROR: see comments in arch/powerpc/tools/head_check.sh
> > 
> 
> How is the associated commit anywhere close to being the cause of this bug?

Sorry about the false report, kindly ignore this. Seems it can't bisect to the actual
bad commit, another similar false report is at [1] with a different bad commit.

We will avoid sending reports on this issue.

[1] https://lore.kernel.org/oe-kbuild-all/202409090839.Gz712lD2-lkp@intel.com/

> 
> -- Steve
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ