From: Jiri Slaby <jslaby@suse.cz>
To: John Johansen <john.johansen@canonical.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 4.14 - BUG: unable to handle kernel paging request at ffffffff3bbbe160 IP: audit_signal_cb+0x75/0xf0
Date: Mon, 27 Nov 2017 20:01:20 +0100 [thread overview]
Message-ID: <620825eb-0e44-f37e-4155-e6780a823b28@suse.cz> (raw)
In-Reply-To: <b31b5553-32c3-344c-ceb7-b2eb9ec7a83a@canonical.com>
On 11/27/2017, 06:59 PM, John Johansen wrote:
> On 11/23/2017 05:38 AM, Jiri Slaby wrote:
>> On 11/22/2017, 04:59 PM, John Johansen wrote:
>>> Can you verify the following patch fixes the problem for you
>>
>> Reportedly, it helps:
>> https://apibugzilla.suse.com/show_bug.cgi?id=1069562#c3
>>
>
> Thanks Jiri,
> Unfortunately I wasn't able to access the bugzilla entry but I assume the reporting and testing comes from Christian Boltz who reported directly to me that it fixed the issue on suse for him. I've added him as a tester to the most recent revision. Let me know if there is someone I am missing that I should credit, or something in the bug I should poke at
Sorry, remove "api" from the URL:
https://bugzilla.suse.com/show_bug.cgi?id=1069562#c3
A comment by Giuseppe Gorgoglione.
--
js
suse labs
next prev parent reply other threads:[~2017-11-27 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 16:58 Shuah Khan
2017-11-21 17:44 ` John Johansen
2017-11-21 18:02 ` Shuah Khan
2017-11-21 23:53 ` John Johansen
2017-11-22 0:28 ` Shuah Khan
2017-11-22 15:59 ` John Johansen
2017-11-23 13:38 ` Jiri Slaby
2017-11-27 17:59 ` John Johansen
2017-11-27 18:09 ` Shuah Khan
2017-11-27 19:01 ` Jiri Slaby [this message]
2017-11-24 10:15 ` Ivan Kozik
2017-11-27 18:08 ` John Johansen
2017-11-27 20:18 ` Shuah Khan
2017-11-30 19:20 ` apparmor: fix oops in audit_signal_cb hook John Johansen
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=620825eb-0e44-f37e-4155-e6780a823b28@suse.cz \
--to=jslaby@suse.cz \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®