From: John Johansen <john.johansen@canonical•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the apparmor tree
Date: Mon, 11 Jul 2022 21:27:12 -0700 [thread overview]
Message-ID: <1c8c926f-5c21-1565-6687-f473400dc065@canonical.com> (raw)
In-Reply-To: <20220712132339.383219ad@canb.auug.org.au>
On 7/11/22 20:23, Stephen Rothwell wrote:
> Hi all,
>
> After merging the apparmor tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> In file included from security/apparmor/include/policy.h:29,
> from security/apparmor/include/policy_ns.h:19,
> from security/apparmor/include/cred.h:19,
> from security/apparmor/net.c:13:
> security/apparmor/net.c: In function 'aa_label_sk_perm':
> security/apparmor/net.c:148:40: error: 'sock' undeclared (first use in this function)
> 148 | struct aa_sk_ctx *ctx = SK_CTX(sock->sk);
> | ^~~~
> security/apparmor/include/net.h:54:21: note: in definition of macro 'SK_CTX'
> 54 | #define SK_CTX(X) ((X)->sk_security)
> | ^
> security/apparmor/net.c:148:40: note: each undeclared identifier is reported only once for each function it appears in
> 148 | struct aa_sk_ctx *ctx = SK_CTX(sock->sk);
> | ^~~~
> security/apparmor/include/net.h:54:21: note: in definition of macro 'SK_CTX'
> 54 | #define SK_CTX(X) ((X)->sk_security)
> | ^
>
> Caused by commit
>
> 6ff81169592d ("apparmor: add a kernel label to use on kernel objects")
>
> I have used the apparmor tree from next-20220711 for today.
>
sorry, the offending patch has been dropped
next prev parent reply other threads:[~2022-07-12 4:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 3:23 linux-next: build failure after merge of the apparmor tree Stephen Rothwell
2022-07-12 4:27 ` John Johansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-02 14:46 Mark Brown
2025-03-26 4:01 Stephen Rothwell
2025-03-26 11:26 ` Jakub Kicinski
2025-03-26 16:19 ` Kuniyuki Iwashima
2025-03-26 16:38 ` Jakub Kicinski
2019-02-08 7:33 Stephen Rothwell
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=1c8c926f-5c21-1565-6687-f473400dc065@canonical.com \
--to=john.johansen@canonical$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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