linux-kernel - Re: [broonie-ci:regmap-test-format] [regmap] af560701e3: RIP:__regmap

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: <53c9f248-84d3-4b85-bf25-59055db7eb54@sirena.org.uk>
Date: Fri, 1 Mar 2024 12:07:56 +0000
From: Mark Brown <broonie@...nel.org>
To: Oliver Sang <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [broonie-ci:regmap-test-format] [regmap]  af560701e3:
 RIP:__regmap_init

On Fri, Mar 01, 2024 at 11:30:13AM +0800, Oliver Sang wrote:
> On Fri, Mar 01, 2024 at 09:37:21AM +0800, Oliver Sang wrote:
> > On Thu, Feb 29, 2024 at 03:47:33PM +0000, Mark Brown wrote:
> > > On Thu, Feb 29, 2024 at 11:43:55PM +0800, kernel test robot wrote:

> > and we noticed there is changes in __regmap_init(), we also noticed the issue
> > seems happen before the test even starts to run. not sure if the detail dmesg in

The patch adds a callback but nothing yet provides that callback, it is
very difficult to see how that might be an issue.

> > https://download.01.org/0day-ci/archive/20240229/202402292329.a1c8a83f-lkp@intel.com/dmesg.xz
> > could supply more information?

> > if you still think this is a wrong report, or you want us to test any patch,
> > please just let us know. it's always our great pleasure. Thanks!

> we checked this issue more, and found it could be platform specific.
> 
> we just try a simple boot with af560701e3 on below machine which we made origial
> report and reproduced the issue (dmesg is attached).
> 
> test machine: 8 threads 1 sockets Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (Kaby Lake) with 32G memory

My best guess would be that this has somehow managed to trigger a
preexisting issue which happens to manifest on whatever platform you're
running.  I can't from the backtrace alone tell where that might be,
there's not enough information about where regmap_init() is being called
from.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)