From: matorola@gmail.com (Anatoly Pugachev)
To: linux-security-module@vger.kernel.org
Subject: [sparc64] kernel unaligned access at TPC aa_dfa_unpack
Date: Tue, 2 Jan 2018 00:11:49 +0300 [thread overview]
Message-ID: <CADxRZqwo8sL3RtEWRMcHkgkSAnWKeVibLRrtdXU2e8w2Q5KSTQ@mail.gmail.com> (raw)
Hello!
Using latest git kernel (4.15.0-rc6) , getting the following messages
on LDOM/kernel boot:
[ 7.693653] Kernel unaligned access at TPC[7496d8] aa_dfa_unpack+0x38/0x580
[ 7.693735] Kernel unaligned access at TPC[7496f8] aa_dfa_unpack+0x58/0x580
[ 7.693782] Kernel unaligned access at TPC[749708] aa_dfa_unpack+0x68/0x580
[ 7.693829] Kernel unaligned access at TPC[74973c] aa_dfa_unpack+0x9c/0x580
[ 7.693875] Kernel unaligned access at TPC[749758] aa_dfa_unpack+0xb8/0x580
[ 7.697135] audit: type=1400 audit(1514840016.480:2):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/sbin/tcpdump" pid=507 comm="apparmor_parser"
Can someone please look, what could cause unaligned access at this
aa_dfa_unpack function/structure ?
kernel config for apparmor is the following:
$ grep APPARMOR /boot/config-4.15.0-rc6
CONFIG_SECURITY_APPARMOR=y
CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
CONFIG_SECURITY_APPARMOR_HASH=y
CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
CONFIG_SECURITY_APPARMOR_DEBUG=y
CONFIG_SECURITY_APPARMOR_DEBUG_ASSERTS=y
# CONFIG_SECURITY_APPARMOR_DEBUG_MESSAGES is not set
CONFIG_DEFAULT_SECURITY_APPARMOR=y
Thanks!
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-01-01 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-01 21:11 Anatoly Pugachev [this message]
2018-01-01 21:42 ` [sparc64] kernel unaligned access at TPC aa_dfa_unpack Sam Ravnborg
2018-01-02 13:56 ` Anatoly Pugachev
2018-01-21 19:41 ` Anatoly Pugachev
2018-02-10 8:10 ` Anatoly Pugachev
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=CADxRZqwo8sL3RtEWRMcHkgkSAnWKeVibLRrtdXU2e8w2Q5KSTQ@mail.gmail.com \
--to=matorola@gmail.com \
--cc=linux-security-module@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 NNTP newsgroup(s).