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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 2 Feb 2023 20:24:00 +0530
From:   Naresh Kamboju <naresh.kamboju@...aro.org>
To:     Mike Kravetz <mike.kravetz@...cle.com>
Cc:     "open list:KERNEL SELFTEST FRAMEWORK" 
        <linux-kselftest@...r.kernel.org>,
        open list <linux-kernel@...r.kernel.org>,
        linux-stable <stable@...r.kernel.org>,
        lkft-triage@...ts.linaro.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Shuah Khan <shuah@...nel.org>, Jeff Xu <jeffxu@...gle.com>,
        Joel Fernandes <joel@...lfernandes.org>,
        Pranith Kumar <bobby.prani@...il.com>,
        David Herrmann <dh.herrmann@...il.com>,
        Anders Roxell <anders.roxell@...aro.org>
Subject: Re: selftests: memfd: run_hugetlbfs_test.sh - invalid opcode: 0000
 [#1] PREEMPT SMP

Hi Mike,

On Wed, 25 Jan 2023 at 06:04, Mike Kravetz <mike.kravetz@...cle.com> wrote:
>
> On 01/05/23 15:14, Naresh Kamboju wrote:
> > While running selftests: memfd: run_hugetlbfs_test.sh on qemu_i386 and i386 the
> > following invalid opcode was noticed on stable-rc 6.1 and  6.0.
> >
> > This is always reproducible on stable-rc 6.1 and  6.0 with qemu_i386 and i386.
> > Build, config and test log details provided in the below links [1].
>
> Hello Naresh,
>
> I have tried to create this issue a few times without success.  Since I
> do not have i386 HW, I am using qemu_i386.  If I use the supplied config,
> my kernel does not boot.  I then try to modify config options which I
> think are not relevant.  By the time I get to a config that will boot, I
> can not recreate the issue. :(
>
> Just curious if you have any suggestions?  Or, Wondering if anyone else has
> suggestions on how to proceed?

Please install tuxmake and run attached script to reproduce reported issues,
$ pip3 install tuxmake
$ ./memfd-crash-test-qemu-i386.sh

This script downloads kernel Image and rootfs and runs run_hugetlbfs_test.sh.
If you have any questions please get back to me.
For your reference I have attached logs.txt

> --
> Mike Kravetz

View attachment "logs.txt" of type "text/plain" (154166 bytes)

Download attachment "memfd-crash-test-qemu-i386.sh" of type "application/x-shellscript" (560 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ