linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiele Zhao <unclexiaole@gmail.com>
To: zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, serge@hallyn.com
Cc: linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Jiele zhao <unclexiaole@gmail.com>
Subject: Re: [PATCH] ima: Fix function name error in comment.
Date: Wed, 31 Mar 2021 09:25:19 +0800	[thread overview]
Message-ID: <0a2d133a-9f12-4e18-cd61-c5d19113dc78@gmail.com> (raw)
In-Reply-To: <20210323091905.317885-1-unclexiaole@gmail.com>

Ping.

On 2021/3/23 17:19, Jiele Zhao wrote:
> Function "ima_file_check" is written as "ima_path_check" in
> the comment. Fix this error to prevent misunderstanding.
>
> Signed-off-by: Jiele Zhao <unclexiaole@gmail.com>
> ---
>   security/integrity/ima/ima_main.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/security/integrity/ima/ima_main.c b/security/integrity/ima/ima_main.c
> index 9ef748ea829f..03bef720ab44 100644
> --- a/security/integrity/ima/ima_main.c
> +++ b/security/integrity/ima/ima_main.c
> @@ -482,7 +482,7 @@ int ima_bprm_check(struct linux_binprm *bprm)
>   }
>   
>   /**
> - * ima_path_check - based on policy, collect/store measurement.
> + * ima_file_check - based on policy, collect/store measurement.
>    * @file: pointer to the file to be measured
>    * @mask: contains MAY_READ, MAY_WRITE, MAY_EXEC or MAY_APPEND
>    *

      parent reply	other threads:[~2021-03-31  1:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23  9:19 [PATCH] ima: Fix function name error in comment Jiele Zhao
2021-03-23 12:46 ` Mimi Zohar
2021-03-31  1:25 ` Jiele Zhao [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=0a2d133a-9f12-4e18-cd61-c5d19113dc78@gmail.com \
    --to=unclexiaole@gmail.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).