mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: "GONG, Ruiqi" <gongruiqi@huaweicloud.com>,
	Paul Moore <paul@paul-moore.com>,
	James Morris <jmorris@namei.org>,
	"Serge E . Hallyn" <serge@hallyn.com>
Cc: apparmor@lists.ubuntu.com, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Xiu Jianfeng <xiujianfeng@huawei.com>,
	Wang Weiyang <wangweiyang2@huawei.com>
Subject: Re: [PATCH] apparmor: remove unused PROF_* macros
Date: Tue, 22 Aug 2023 12:28:18 -0700	[thread overview]
Message-ID: <6d9e4dd9-4197-bbd1-eaf5-d79db0605ea3@canonical.com> (raw)
In-Reply-To: <20230807093904.565766-1-gongruiqi@huaweicloud.com>

On 8/7/23 02:39, GONG, Ruiqi wrote:
> From: "GONG, Ruiqi" <gongruiqi1@huawei.com>
> 
> The last usage of PROF_{ADD,REPLACE} were removed by commit 18e99f191a8e
> ("apparmor: provide finer control over policy management"). So remove
> these two unused macros.
> 
> Signed-off-by: GONG, Ruiqi <gongruiqi1@huawei.com>

sorry, I seem to have dropped my reply to this, I have
pulled this into apparmor-next

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

> ---
>   security/apparmor/include/policy.h | 3 ---
>   1 file changed, 3 deletions(-)
> 
> diff --git a/security/apparmor/include/policy.h b/security/apparmor/include/policy.h
> index 545f791cabda..ed9a8669af80 100644
> --- a/security/apparmor/include/policy.h
> +++ b/security/apparmor/include/policy.h
> @@ -254,9 +254,6 @@ ssize_t aa_remove_profiles(struct aa_ns *view, struct aa_label *label,
>   			   char *name, size_t size);
>   void __aa_profile_list_release(struct list_head *head);
>   
> -#define PROF_ADD 1
> -#define PROF_REPLACE 0
> -
>   #define profile_unconfined(X) ((X)->mode == APPARMOR_UNCONFINED)
>   
>   /**


      reply	other threads:[~2023-08-22 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  9:39 GONG, Ruiqi
2023-08-22 19:28 ` 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=6d9e4dd9-4197-bbd1-eaf5-d79db0605ea3@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=apparmor@lists.ubuntu.com \
    --cc=gongruiqi@huaweicloud.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=serge@hallyn.com \
    --cc=wangweiyang2@huawei.com \
    --cc=xiujianfeng@huawei.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

all inboxes | Powered by JetHome®