mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: "Günther Noack" <gnoack3000@gmail.com>,
	"Tanya Agarwal" <tanyaagarwal25699@gmail.com>
Cc: casey@schaufler-ca.com, takedakn@nttdata.co.jp,
	penguin-kernel@i-love.sakura.ne.jp, john.johansen@canonical.com,
	paul@paul-moore.com, jmorris@namei.org, serge@hallyn.com,
	roberto.sassu@huawei.com, dmitry.kasatkin@gmail.com,
	eric.snowberg@oracle.com, mic@digikod.net, gnoack@google.com,
	stephen.smalley.work@gmail.com, omosnace@redhat.com,
	linux-kernel@vger.kernel.org, apparmor@lists.ubuntu.com,
	linux-security-module@vger.kernel.org,
	linux-integrity@vger.kernel.org, skhan@linuxfoundation.org,
	anupnewsmail@gmail.com
Subject: Re: [PATCH V2] security: fix typos and spelling errors
Date: Mon, 13 Jan 2025 14:19:23 -0500	[thread overview]
Message-ID: <d1b05612412a1d4b858662f296b45279c2141aa8.camel@linux.ibm.com> (raw)
In-Reply-To: <20250113.a860b47a11c7@gnoack.org>

On Mon, 2025-01-13 at 15:50 +0100, Günther Noack wrote:
> On Sun, Jan 12, 2025 at 12:59:27PM +0530, Tanya Agarwal wrote:
> > From: Tanya Agarwal <tanyaagarwal25699@gmail.com>
> > 
> > Fix typos and spelling errors in security module comments that were
> > identified using the codespell tool.
> > No functional changes - documentation only.
> > 
> > Signed-off-by: Tanya Agarwal <tanyaagarwal25699@gmail.com>
> > ---
> > Thanks Günther, for catching this error.
> > The irony of having a spelling mistake in a patch that fixes spelling
> > mistakes is not lost on me :) 
> > 
> > I've fixed it in V2 of the patch. Thank you for the careful review!
> > 
> > V2: fix spelling mistake - s/beeen/been/ 
> > 
> >  security/apparmor/apparmorfs.c      | 6 +++---
> >  security/apparmor/domain.c          | 4 ++--
> >  security/apparmor/label.c           | 2 +-
> >  security/apparmor/lsm.c             | 2 +-
> >  security/apparmor/policy.c          | 4 ++--
> >  security/integrity/evm/evm_crypto.c | 2 +-
> >  security/integrity/evm/evm_main.c   | 2 +-
> >  security/integrity/ima/ima_main.c   | 6 +++---
> >  security/landlock/ruleset.c         | 2 +-
> >  security/selinux/avc.c              | 2 +-
> >  security/smack/smack.h              | 2 +-
> >  security/smack/smack_access.c       | 4 ++--
> >  security/smack/smack_lsm.c          | 6 +++---
> >  security/smack/smackfs.c            | 2 +-
> >  security/tomoyo/domain.c            | 2 +-
> >  15 files changed, 24 insertions(+), 24 deletions(-)
> > 
> 
> [...]
> 
> > diff --git a/security/integrity/ima/ima_main.c
> > b/security/integrity/ima/ima_main.c
> > index 9b87556b03a7..cdb8c7419d7e 100644
> > --- a/security/integrity/ima/ima_main.c
> > +++ b/security/integrity/ima/ima_main.c
> > @@ -983,9 +983,9 @@ int process_buffer_measurement(struct mnt_idmap *idmap,
> >  	}
> >  
> >  	/*
> > -	 * Both LSM hooks and auxilary based buffer measurements are
> > -	 * based on policy.  To avoid code duplication, differentiate
> > -	 * between the LSM hooks and auxilary buffer measurements,
> > +	 * Both LSM hooks and auxiliary based buffer measurements are
> > +	 * based on policy. To avoid code duplication, differentiate
>                           ^^^
> 
> (Small nit:) This change from two-spaces-after-the-dot to a single
> space looks like it happened accidentally.  The two-space style is
> dominant in the ima_main.c file.
> 
> (However, I am not involved in IMA and others have more authority to
> review this part.  As Paul also said, reviews tend to go smoother when
> the scope for the patch is a single subsystem - it makes the
> responsibilities clearer.)
> 
> > +	 * between the LSM hooks and auxiliary buffer measurements,

The spelling mistake being corrected in two places is auxilary -> auxiliary.  Thank
you for noticing the unnecessary change from two spaces to one space as well.

FYI, I agree with Paul the patch should be split.

Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>


> >  	 * retrieving the policy rule information only for the LSM hook
> >  	 * buffer measurements.
> >  	 */
> 
> –Günther


  reply	other threads:[~2025-01-13 19:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11 19:41 [PATCH] " Tanya Agarwal
2025-01-11 22:57 ` Günther Noack
2025-01-12  7:29   ` [PATCH V2] " Tanya Agarwal
2025-01-12 16:36     ` Paul Moore
2025-01-12 23:59       ` Tetsuo Handa
2025-01-13  2:56         ` Paul Moore
2025-01-13 14:50     ` Günther Noack
2025-01-13 19:19       ` Mimi Zohar [this message]
2025-01-14 16:13         ` Tanya Agarwal
2025-01-15  0:18           ` Paul Moore

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=d1b05612412a1d4b858662f296b45279c2141aa8.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=anupnewsmail@gmail.com \
    --cc=apparmor@lists.ubuntu.com \
    --cc=casey@schaufler-ca.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=eric.snowberg@oracle.com \
    --cc=gnoack3000@gmail.com \
    --cc=gnoack@google.com \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mic@digikod.net \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=roberto.sassu@huawei.com \
    --cc=serge@hallyn.com \
    --cc=skhan@linuxfoundation.org \
    --cc=stephen.smalley.work@gmail.com \
    --cc=takedakn@nttdata.co.jp \
    --cc=tanyaagarwal25699@gmail.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®