From: Mike Kravetz <mike.kravetz@oracle.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Cc: "open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>, Jeff Xu <jeffxu@google.com>,
Joel Fernandes <joel@joelfernandes.org>,
Pranith Kumar <bobby.prani@gmail.com>,
David Herrmann <dh.herrmann@gmail.com>
Subject: Re: selftests: memfd: run_hugetlbfs_test.sh - invalid opcode: 0000 [#1] PREEMPT SMP
Date: Thu, 2 Feb 2023 13:54:23 -0800 [thread overview]
Message-ID: <Y9wxD0ngdo832Az5@monkey> (raw)
In-Reply-To: <CADYN=9+=p0cYu63feXfZVXZTGruJP_i5dA3AuP0G6Fh_rfQO0g@mail.gmail.com>
On 02/02/23 16:29, Anders Roxell wrote:
> On Thu, 2 Feb 2023 at 15:54, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > Hi Mike,
> >
> > On Wed, 25 Jan 2023 at 06:04, Mike Kravetz <mike.kravetz@oracle.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
>
> oops, a typo, should be 'tuxrun' not 'tuxmake'.
>
> https://tuxrun.org/
>
> Cheers,
> Anders
>
> > $ ./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
Sorry, I am still a bit confused.
Was the intention to attach the script 'memfd-crash-test-qemu-i386.sh'?
The only attachment I have seen is 'logs.txt' which is the output of the run.
--
Mike Kravetz
next prev parent reply other threads:[~2023-02-02 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 9:44 selftests: memfd: run_hugetlbfs_test.sh - invalid opcode: 0000 [#1] PREEMPT SMP Naresh Kamboju
2023-01-25 0:34 ` Mike Kravetz
2023-02-02 14:54 ` Naresh Kamboju
2023-02-02 15:29 ` Anders Roxell
2023-02-02 21:54 ` Mike Kravetz [this message]
2023-02-03 7:00 ` Naresh Kamboju
2023-02-04 1:11 ` Mike Kravetz
2023-02-02 14:59 ` Naresh Kamboju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y9wxD0ngdo832Az5@monkey \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=bobby.prani@gmail.com \
--cc=dh.herrmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jeffxu@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.