public inbox for kernel-tls-handshake@lists.linux.dev
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: <kernel-tls-handshake@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 5/5] tlshd: Relocate TLSHD_ALLPERMS
Date: Tue, 10 Jun 2025 09:25:50 -0400	[thread overview]
Message-ID: <20250610132550.39715-6-cel@kernel.org> (raw)
In-Reply-To: <20250610132550.39715-1-cel@kernel.org>

From: Chuck Lever <chuck.lever@oracle.com>

Clean up: Move it next to the other related macro definitions.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 src/tlshd/config.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/src/tlshd/config.c b/src/tlshd/config.c
index b41051e40c08..df26663d3a69 100644
--- a/src/tlshd/config.c
+++ b/src/tlshd/config.c
@@ -46,12 +46,6 @@
 
 static GKeyFile *tlshd_configuration;
 
-/**
- * ALLPERMS exists in glibc, but not on musl, so we
- * manually define TLSHD_ACCESSPERMS instead of using ALLPERMS.
- */
-#define TLSHD_ACCESSPERMS	(S_IRWXU|S_IRWXG|S_IRWXO)
-
 /**
  * tlshd_config_init - Read tlshd's config file
  * @pathname: Pathname to config file
@@ -120,6 +114,12 @@ void tlshd_config_shutdown(void)
 	g_key_file_free(tlshd_configuration);
 }
 
+/**
+ * ALLPERMS exists in glibc, but not on musl, so we manually
+ * define TLSHD_ACCESSPERMS instead of using ALLPERMS.
+ */
+#define TLSHD_ACCESSPERMS	(S_IRWXU|S_IRWXG|S_IRWXO)
+
 /*
  * Expected file attributes
  */
-- 
2.49.0


      parent reply	other threads:[~2025-06-10 13:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10 13:25 [PATCH 0/5] Kick off ktls-utils 1.2 development Chuck Lever
2025-06-10 13:25 ` [PATCH 1/5] tlshd: Fix a minor race Chuck Lever
2025-06-10 13:25 ` [PATCH 2/5] tlshd: Remove unneeded variable "error" Chuck Lever
2025-06-10 13:25 ` [PATCH 3/5] workflows: Limit permission of the makefile.yml action Chuck Lever
2025-06-10 13:25 ` [PATCH 4/5] tlshd: Add default keyrings for NFS Chuck Lever
2025-06-10 13:25 ` Chuck Lever [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=20250610132550.39715-6-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=kernel-tls-handshake@lists.linux.dev \
    /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