public inbox for linux-security-module@vger.kernel.org
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: Ryota Sakamoto <sakamo.ryota@gmail.com>,
	Paul Moore <paul@paul-moore.com>,
	James Morris <jmorris@namei.org>,
	"Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-kernel@vger.kernel.org, apparmor@lists.ubuntu.com,
	linux-security-module@vger.kernel.org
Subject: Re: [PATCH] apparmor: add .kunitconfig
Date: Wed, 4 Feb 2026 23:41:15 -0800	[thread overview]
Message-ID: <1695a9cc-0d50-48f3-8c44-c84f3424924f@canonical.com> (raw)
In-Reply-To: <20260125-add-apparmor-kunitconfig-v1-1-e815cec415df@gmail.com>

On 1/25/26 02:05, Ryota Sakamoto wrote:
> Add .kunitconfig file to the AppArmor directory to enable easy execution of
> KUnit tests.
> 
> AppArmor tests (CONFIG_SECURITY_APPARMOR_KUNIT_TEST) depend on
> CONFIG_SECURITY_APPARMOR which also depends on CONFIG_SECURITY and
> CONFIG_NET. Without explicitly enabling these configs in the .kunitconfig,
> developers will need to specify config manually.
> 
> With the .kunitconfig, developers can run the tests:
>    $ ./tools/testing/kunit/kunit.py run --kunitconfig security/apparmor
> 
> Signed-off-by: Ryota Sakamoto <sakamo.ryota@gmail.com>

Acked-by: John Johansen <john.johansen@canonical.com>

sorry, for the delay I actually pulled this in a while ago, but the initial reply seems
to have gone into the void.

> ---
>   security/apparmor/.kunitconfig | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/security/apparmor/.kunitconfig b/security/apparmor/.kunitconfig
> new file mode 100644
> index 0000000000000000000000000000000000000000..aa842a0266e9d33c3333ec2ea180206187b0eb4c
> --- /dev/null
> +++ b/security/apparmor/.kunitconfig
> @@ -0,0 +1,5 @@
> +CONFIG_KUNIT=y
> +CONFIG_NET=y
> +CONFIG_SECURITY=y
> +CONFIG_SECURITY_APPARMOR=y
> +CONFIG_SECURITY_APPARMOR_KUNIT_TEST=y
> 
> ---
> base-commit: d91a46d6805af41e7f2286e0fc22d498f45a682b
> change-id: 20260125-add-apparmor-kunitconfig-28aba43c1580
> 
> Best regards,


      reply	other threads:[~2026-02-05  7:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-25 10:05 [PATCH] apparmor: add .kunitconfig Ryota Sakamoto
2026-02-05  7:41 ` 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=1695a9cc-0d50-48f3-8c44-c84f3424924f@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=apparmor@lists.ubuntu.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=sakamo.ryota@gmail.com \
    --cc=serge@hallyn.com \
    /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