From: Anatoly Pugachev <matorola@gmail.com>
To: Colin Ian King <colin.king@canonical.com>
Cc: Sparc kernel list <sparclinux@vger.kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
debian-sparc <debian-sparc@lists.debian.org>,
kernel-testers@vger.kernel.org
Subject: Re: [sparc64] kernel panic from running a program in userspace
Date: Sat, 19 Jun 2021 12:45:45 +0300 [thread overview]
Message-ID: <CADxRZqz6EZ-K+mWn4A5kp9yZEt1v1YjmFqeZNcf+W99fT2dm8w@mail.gmail.com> (raw)
In-Reply-To: <f9bd5a0e-6f9e-c042-cbfc-2e03bf16b92c@canonical.com>
On Sat, Jun 19, 2021 at 12:31 PM Colin Ian King
<colin.king@canonical.com> wrote:
>
> Hi,
>
> I suspect this issue was fixed with the following commit:
>
> commit e5e8b80d352ec999d2bba3ea584f541c83f4ca3f
> Author: Rob Gardner <rob.gardner@oracle.com>
> Date: Sun Feb 28 22:48:16 2021 -0700
>
> sparc64: Fix opcode filtering in handling of no fault loads
Colin,
yes, but I believe that it was quite a different kernel bug.
Besides, my current kernel test is based on git kernel 5.13.0-rc6
(released last monday), which already includes the mentioned 'opcode'
fix.
> > stress-ng.git$ ./stress-ng --verbose --timeout 10m --opcode -1
> > stress-ng: debug: [480950] stress-ng 0.12.10 g27f90a2276bd
> > stress-ng: debug: [480950] system: Linux ttip 5.13.0-rc6 #229 SMP Tue
> > Jun 15 12:30:23 MSK 2021 sparc64
> > stress-ng: debug: [480950] RAM total: 7.8G, RAM free: 7.0G, swap free: 768.7M
> > stress-ng: debug: [480950] 8 processors online, 256 processors configured
> > stress-ng: info: [480950] dispatching hogs: 8 opcode
prev parent reply other threads:[~2021-06-19 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 8:24 [sparc64] kernel panic from running a program in userspace Anatoly Pugachev
2021-06-19 9:30 ` Colin Ian King
2021-06-19 9:45 ` Anatoly Pugachev [this message]
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=CADxRZqz6EZ-K+mWn4A5kp9yZEt1v1YjmFqeZNcf+W99fT2dm8w@mail.gmail.com \
--to=matorola@gmail.com \
--cc=colin.king@canonical.com \
--cc=debian-sparc@lists.debian.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).