From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org
Subject: Re: [PATCH 6.6.y 2/2] apparmor: Fix & Optimize table creation from possibly unaligned memory
Date: Wed, 07 Oct 2026 20:49:37 +0000 [thread overview]
Message-ID: <sashiko-outbox-163353@kernel.org> (raw)
In-Reply-To: <20261007204226.47033-3-artem@trailofbits.com>
> From: Helge Deller <deller@kernel.org>
>
> [ Upstream commit 6fc367bfd4c8886e6b1742aabbd1c0bdc310db3a ]
>
> Source blob may come from userspace and might be unaligned.
> Try to optize the copying process by avoiding unaligned memory accesses.
>
> - Added Fixes tag
> - Added "Fix &" to description as this doesn't just optimize but fixes
> a potential unaligned memory access
> Fixes: e6e8bf418850d ("apparmor: fix restricted endian type warnings for dfa unpack")
> Signed-off-by: Helge Deller <deller@gmx.de>
> [jj: remove duplicate word "convert" in comment trigger checkpatch warning]
> Signed-off-by: John Johansen <john.johansen@canonical.com>
> Assisted-by: LLM
> Signed-off-by: Artem Dinaburg <artem@trailofbits.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261007204226.47033-1-artem@trailofbits.com?part=2
next prev parent reply other threads:[~2026-10-07 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 20:42 [PATCH 6.6.y 0/2] apparmor: backport CVE-2026-45893, CVE-2026-46254 Artem Dinaburg
2026-10-07 20:42 ` [PATCH 6.6.y 1/2] AppArmor: Allow apparmor to handle unaligned dfa tables Artem Dinaburg
2026-10-07 20:51 ` sashiko-bot
2026-10-07 20:42 ` [PATCH 6.6.y 2/2] apparmor: Fix & Optimize table creation from possibly unaligned memory Artem Dinaburg
2026-10-07 20:49 ` sashiko-bot [this message]
2026-10-08 5:56 ` [PATCH 6.6.y 0/2] apparmor: backport CVE-2026-45893, CVE-2026-46254 Sasha Levin
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=sashiko-outbox-163353@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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