linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tóth János via B4 Relay" <devnull+gomba007.gmail.com@kernel.org>
To: Casey Schaufler <casey@schaufler-ca.com>,
	Paul Moore <paul@paul-moore.com>,
	James Morris <jmorris@namei.org>,
	"Serge E. Hallyn" <serge@hallyn.com>
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Tóth János" <gomba007@gmail.com>
Subject: [PATCH RESEND] security: smack: smackfs: fix typo (lables->labels)
Date: Thu, 20 Jul 2023 12:45:22 +0200	[thread overview]
Message-ID: <20230720-smackfs-lables-fix-v1-1-7994a1f7e45a@gmail.com> (raw)

From: Tóth János <gomba007@gmail.com>

Fix a spelling error in smakcfs.

Signed-off-by: Tóth János <gomba007@gmail.com>
---
 security/smack/smackfs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/security/smack/smackfs.c b/security/smack/smackfs.c
index 5590eaad241b..2b79c30d4bb6 100644
--- a/security/smack/smackfs.c
+++ b/security/smack/smackfs.c
@@ -114,7 +114,7 @@ struct smack_known *smack_syslog_label;
  * SMACK_PTRACE_DEFAULT    regular smack ptrace rules (/proc based)
  * SMACK_PTRACE_EXACT      labels must match, but can be overriden with
  *			   CAP_SYS_PTRACE
- * SMACK_PTRACE_DRACONIAN  lables must match, CAP_SYS_PTRACE has no effect
+ * SMACK_PTRACE_DRACONIAN  labels must match, CAP_SYS_PTRACE has no effect
  */
 int smack_ptrace_rule = SMACK_PTRACE_DEFAULT;
 

---
base-commit: 6995e2de6891c724bfeb2db33d7b87775f913ad1
change-id: 20230706-smackfs-lables-fix-ac965c4c479f

Best regards,
-- 
Tóth János <gomba007@gmail.com>


             reply	other threads:[~2023-07-20 10:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 10:45 Tóth János via B4 Relay [this message]
2023-07-20 14:59 ` [PATCH RESEND] security: smack: smackfs: fix typo (lables->labels) Casey Schaufler

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=20230720-smackfs-lables-fix-v1-1-7994a1f7e45a@gmail.com \
    --to=devnull+gomba007.gmail.com@kernel.org \
    --cc=casey@schaufler-ca.com \
    --cc=gomba007@gmail.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 \
    /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).