From: Shuah Khan <shuahkh@osg.samsung.com>
To: John Johansen <john.johansen@canonical.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>
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 13:18:45 -0700 [thread overview]
Message-ID: <30c0a4fc-7461-524e-17fe-bbe6622d0e11@osg.samsung.com> (raw)
In-Reply-To: <95f7ed8a-0434-0203-2555-557058d71210@canonical.com>
On 11/27/2017 11:08 AM, John Johansen wrote:
> On 11/21/2017 04:28 PM, Shuah Khan wrote:
>> On 11/21/2017 04:53 PM, John Johansen wrote:
>>> On 11/21/2017 10:02 AM, Shuah Khan wrote:
>>>> On 11/21/2017 10:44 AM, John Johansen wrote:
>>>>> On 11/21/2017 08:58 AM, Shuah Khan wrote:
>>>>>> Hi John,
>>>>>>
>>>>>> I am seeing the following on my laptop. Unfortunately this is my primary
>>>>>> system and my ability to bisect might be a bit limited. The system is
>>>>>> running
>>>>>>
>>>>>> 4.14.0+ #4 SMP Tue Nov 14 19:25:58 MST 2017 x86_64 x86_64 x86_64 GNU/Linux
>>>>>>
>>>>>> on Ubuntu 17.10 base.
>>>>>>
>>>>>> Is this a known issue? Please see the dmesg excerpts below:
>>>>>>
>>>>> Its not. I'll start looking into it today
>>>>>
>>>>> Do you have any other information that you can send to me?
>>>>>
>>>>> Any particular task/work load that triggers this?
>>>>> Can you tar up your /etc/apparmor.d/ and send that to me?
>>>>>
>>>>>
>>>>
>>>> Yeah. I forgot mention that detail :)
>>>>
>>> So my first attempts to replicate have failed.
>>>
>>> Can you confirm the sha of your kernel build? If its has some none upstream patches can you provide the sha your kernel is based on.
>>>
>>> My testing so far were based on bebc6082da0a9f5d47a1ea2edc099bf671058bd4
>>>
>>>
>>> Can you also send me your kernel config so I can better replicate your build
>>>
>>
>> commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4 (tag: v4.14)
>> Author: Linus Torvalds <torvalds@linux-foundation.org>
>> Date: Sun Nov 12 10:46:13 2017 -0800
>>
>> Linux 4.14
>>
>> The above is the top commit in my tree. Config attached.
>>
>
> thanks Shuah,
>
> find below the latest revision of the patch. Nothing has changed code
> wise but I have added Tested-by: entries for the 3 people of have
> tested it and reported it working for them, and also added Cc: stable
> entry.
>
> ---
>
>>From d198240cace036c7d1e502fd20fe416df4fd8c24 Mon Sep 17 00:00:00 2001
> From: John Johansen <john.johansen@canonical.com>
> Date: Wed, 22 Nov 2017 07:33:38 -0800
> Subject: [PATCH] apparmor: fix oops in audit_signal_cb hook
>
I am not seeing the problem with this patch. I opened a couple
of files with evince. Looks good to me so far.
Tested-by: Shuah Khan <shuahkh@osg.samsung.com>
thanks,
-- Shuah
next prev parent reply other threads:[~2017-11-27 20:19 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
2017-11-24 10:15 ` Ivan Kozik
2017-11-27 18:08 ` John Johansen
2017-11-27 20:18 ` Shuah Khan [this message]
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=30c0a4fc-7461-524e-17fe-bbe6622d0e11@osg.samsung.com \
--to=shuahkh@osg.samsung.com \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--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®