From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Stephen Smalley <stephen.smalley.work@gmail.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
X86 ML <x86@kernel.org>,
selinux@vger.kernel.org, open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
paul@paul-moore.com, Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
omosnace@redhat.com, rgb@redhat.com,
Kees Cook <keescook@chromium.org>,
Casey Schaufler <casey@schaufler-ca.com>,
YueHaibing <yuehaibing@huawei.com>,
jeffv@google.com, Kent Overstreet <kent.overstreet@gmail.com>
Subject: Re: Linux-next: Kernel panic - not syncing: Fatal exception in interrupt - RIP: 0010:security_port_sid
Date: Thu, 20 Aug 2020 08:31:11 +1000 [thread overview]
Message-ID: <20200820083111.46e81b4c@canb.auug.org.au> (raw)
In-Reply-To: <fdffd8f2-ea67-4bfd-f75b-9ffd56dfbbde@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
Hi all,
On Wed, 19 Aug 2020 11:12:44 -0400 Stephen Smalley <stephen.smalley.work@gmail.com> wrote:
>
> Fix can be found at:https://patchwork.kernel.org/patch/11724203/
> <https://patchwork.kernel.org/patch/11724203/>
Thanks.
I will add that to the selinux tree merge in linux-next until it turns
up in the tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-08-19 22:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 10:11 Linux-next: Kernel panic - not syncing: Fatal exception in interrupt - RIP: 0010:security_port_sid Naresh Kamboju
2020-08-19 12:28 ` Stephen Smalley
2020-08-19 13:12 ` Paul Moore
2020-08-19 13:16 ` Stephen Smalley
2020-08-19 13:28 ` Paul Moore
2020-08-19 15:06 ` Andy Shevchenko
2020-08-19 15:12 ` Stephen Smalley
2020-08-19 15:38 ` Andy Shevchenko
2020-08-19 22:31 ` Stephen Rothwell [this message]
2020-08-20 1:21 ` Paul Moore
2020-08-20 2:36 ` Stephen Rothwell
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=20200820083111.46e81b4c@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=andy.shevchenko@gmail.com \
--cc=casey@schaufler-ca.com \
--cc=eparis@parisplace.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeffv@google.com \
--cc=keescook@chromium.org \
--cc=kent.overstreet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=stephen.smalley.work@gmail.com \
--cc=x86@kernel.org \
--cc=yuehaibing@huawei.com \
/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