From: Mike Kravetz <mike.kravetz@oracle.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
"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: Fri, 3 Feb 2023 17:11:22 -0800 [thread overview]
Message-ID: <Y92wupl9Bw+PO2/Z@monkey> (raw)
In-Reply-To: <CA+G9fYs92bgdfYGj7uudnnnUA7hm82sggpWmSjwdKA9qjZvW7A@mail.gmail.com>
On 02/03/23 12:30, Naresh Kamboju wrote:
> On Fri, 3 Feb 2023 at 03:24, Mike Kravetz <mike.kravetz@oracle.com> wrote:
> > On 02/02/23 16:29, Anders Roxell wrote:
> > > On Thu, 2 Feb 2023 at 15:54, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
>
> I have sent you a private email with a reproducer script.
>
Thanks! I can reproduce with the script.
Not as good as being able to build (and modify) my own kernel, but it
may provide more clues.
--
Mike Kravetz
next prev parent reply other threads:[~2023-02-04 1:11 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
2023-02-03 7:00 ` Naresh Kamboju
2023-02-04 1:11 ` Mike Kravetz [this message]
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=Y92wupl9Bw+PO2/Z@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.