linux-kernel - Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c

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: <CA+G9fYvCX5fd5dHdaGpQ7wpZNcea-=vtuhapW00D8AUkE5VUqA@mail.gmail.com>
Date:   Thu, 17 Jun 2021 17:45:34 +0530
From:   Naresh Kamboju <naresh.kamboju@...aro.org>
To:     Will Deacon <will@...nel.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        linux-mm <linux-mm@...ck.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        open list <linux-kernel@...r.kernel.org>,
        lkft-triage@...ts.linaro.org, regressions@...ts.linux.dev,
        Andrew Morton <akpm@...ux-foundation.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Arnd Bergmann <arnd@...db.de>,
        Ard Biesheuvel <ardb@...nel.org>,
        Catalin Marinas <catalin.marinas@....com>,
        Mike Rapoport <rppt@...ux.ibm.com>,
        Christophe Leroy <christophe.leroy@...roup.eu>
Subject: Re: [next] [arm64] kernel BUG at arch/arm64/mm/physaddr.c

Hi Will,

On Tue, 15 Jun 2021 at 17:20, Will Deacon <will@...nel.org> wrote:
>
> Hi Naresh,
>
> On Tue, Jun 15, 2021 at 04:41:25PM +0530, Naresh Kamboju wrote:
> > Following kernel crash reported while boot linux next 20210615 tag on qemu_arm64
> > with allmodconfig build.

<trim>

> Thanks for the report, although since this appears to be part of a broader
> testing effort, here are some things that I think would make the reports
> even more useful:
>
>   1. An indication as to whether or not this is a regression (i.e. do you
>      have a known good build, perhaps even a bisection?)
>
>   2. Either a link to the vmlinux, or faddr2line run on the backtrace.
>      Looking at the above, I can't tell what sparse_init_nid+0x98/0x6d0
>      actually is.
>
>   3. The exact QEMU command-line you are using, so I can try to reproduce
>      this locally. I think the 0-day bot wraps the repro up in a shell
>      script for you.
>
>   4. Whether or not the issue is reproducible.
>
>   5. Information about the toolchain you used to build the kernel (it
>      happens to be present here because it's in the kernel log, but
>      generally I think it would be handy to specify that in the report).
>
> Please can you provide that information for this crash? It would really
> help in debugging it.

Sorry for the incomplete bug report.

Thanks for sharing these details.
Next time I will include the suggested data points in my email report.

- Naresh