From: Randy Dunlap <rdunlap@infradead.org>
To: Mark Brown <broonie@kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org, apparmor@lists.ubuntu.com,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
John Johansen <john.johansen@canonical.com>,
John Johansen <john@apparmor.net>,
Georgia Garcia <georgia.garcia@canonical.com>
Subject: Re: linux-next: Tree for Jul 29 (apparmor)
Date: Wed, 29 Jul 2026 20:52:34 -0700 [thread overview]
Message-ID: <ecdde049-968d-4a89-a0e1-4f00a099fe04@infradead.org> (raw)
In-Reply-To: <amoeme309Gay4S5M@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
On 7/29/26 8:39 AM, Mark Brown wrote:
> Hi all,
>
> Changes since 20260728:
>
apparmorfs.c makes calls into zstd_*() even when
CONFIG_SECURITY_APPARMOR_EXPORT_BINARY is not set, causing
build errors:
/usr/bin/ld.bfd: security/apparmor/apparmorfs.o: in function `policy_update':
apparmorfs.c:(.text+0x1307): undefined reference to `zstd_get_frame_header'
/usr/bin/ld.bfd: apparmorfs.c:(.text+0x1359): undefined reference to `zstd_dctx_workspace_bound'
/usr/bin/ld.bfd: apparmorfs.c:(.text+0x13f7): undefined reference to `zstd_init_dctx'
/usr/bin/ld.bfd: apparmorfs.c:(.text+0x140c): undefined reference to `zstd_decompress_dctx'
/usr/bin/ld.bfd: apparmorfs.c:(.text+0x1411): undefined reference to `zstd_is_error'
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r1406.gz --]
[-- Type: application/gzip, Size: 34307 bytes --]
next parent reply other threads:[~2026-07-30 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <amoeme309Gay4S5M@sirena.org.uk>
2026-07-30 3:52 ` Randy Dunlap [this message]
2026-07-30 13:47 ` linux-next: Tree for Jul 29 (apparmor) 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=ecdde049-968d-4a89-a0e1-4f00a099fe04@infradead.org \
--to=rdunlap@infradead.org \
--cc=apparmor@lists.ubuntu.com \
--cc=broonie@kernel.org \
--cc=georgia.garcia@canonical.com \
--cc=john.johansen@canonical.com \
--cc=john@apparmor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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