From: John Johansen <john.johansen@canonical.com>
To: torvalds@linux-foundation.org
Cc: Shuah Khan <shuahkh@osg.samsung.com>, linux-kernel@vger.kernel.org
Subject: apparmor: fix oops in audit_signal_cb hook
Date: Thu, 30 Nov 2017 11:20:28 -0800 [thread overview]
Message-ID: <59eeb073-2afd-f1fc-c0a7-d70b90d11715@canonical.com> (raw)
In-Reply-To: <5f0f4166-04b3-04de-16e7-884500ad03ca@osg.samsung.com>
Linus,
can you please pull this fix for an oops that unfortunately on surfaced after
4.14 was released.
thanks
-- John
The following changes since commit bebc6082da0a9f5d47a1ea2edc099bf671058bd4:
Linux 4.14 (2017-11-12 10:46:13 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor tags/apparmor-pr-2017-11-30
for you to fetch changes up to b12cbb21586277f72533769832c24cc6c1d60ab3:
apparmor: fix oops in audit_signal_cb hook (2017-11-27 14:38:15 -0800)
----------------------------------------------------------------
bug fixes:
- apparmor: fix oops in audit_signal_cb hook
----------------------------------------------------------------
John Johansen (1):
apparmor: fix oops in audit_signal_cb hook
security/apparmor/include/audit.h | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
prev parent reply other threads:[~2017-11-30 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 16:58 Linux 4.14 - BUG: unable to handle kernel paging request at ffffffff3bbbe160 IP: audit_signal_cb+0x75/0xf0 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
2017-11-30 19:20 ` John Johansen [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=59eeb073-2afd-f1fc-c0a7-d70b90d11715@canonical.com \
--to=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®