From: John Johansen <john.johansen@canonical.com>
To: Colin King <colin.king@canonical.com>,
James Morris <james.l.morris@oracle.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
linux-security-module@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apparmor: fix spelling mistake: "resoure" -> "resource"
Date: Mon, 25 Sep 2017 10:24:02 -0400 [thread overview]
Message-ID: <358b9115-2dbe-0a63-12e5-27b4c8e8d76d@canonical.com> (raw)
In-Reply-To: <20170824083145.18799-1-colin.king@canonical.com>
On 08/24/2017 04:31 AM, Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> Trivial fix to spelling mistake in comment and also with text in
> audit_resource call.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> security/apparmor/resource.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/security/apparmor/resource.c b/security/apparmor/resource.c
> index d8bc842594ed..cf4d234febe9 100644
> --- a/security/apparmor/resource.c
> +++ b/security/apparmor/resource.c
> @@ -47,7 +47,7 @@ static void audit_cb(struct audit_buffer *ab, void *va)
> /**
> * audit_resource - audit setting resource limit
> * @profile: profile being enforced (NOT NULL)
> - * @resoure: rlimit being auditing
> + * @resource: rlimit being auditing
> * @value: value being set
> * @error: error value
> *
> @@ -128,7 +128,7 @@ int aa_task_setrlimit(struct aa_label *label, struct task_struct *task,
> error = fn_for_each(label, profile,
> audit_resource(profile, resource,
> new_rlim->rlim_max, peer,
> - "cap_sys_resoure", -EACCES));
> + "cap_sys_resource", -EACCES));
> else
> error = fn_for_each_confined(label, profile,
> profile_setrlimit(profile, resource, new_rlim));
>
pulled in to apparmor-next
prev parent reply other threads:[~2017-09-25 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 8:31 Colin King
2017-09-25 14:24 ` 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=358b9115-2dbe-0a63-12e5-27b4c8e8d76d@canonical.com \
--to=john.johansen@canonical.com \
--cc=colin.king@canonical.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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
all inboxes | Powered by JetHome®