From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Daniel Gomez <da.gomez@samsung.com>
Subject: [PATCH v2 1/4] guestfs: Fix definition of guestfs_storage_dir
Date: Mon, 14 Apr 2025 13:05:43 -0400 [thread overview]
Message-ID: <20250414170546.1995982-2-cel@kernel.org> (raw)
In-Reply-To: <20250414170546.1995982-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
{{ kdevops_storage_pool_path }} already ends with "/kdevops", so
remove that string from the end of guestfs_storage_dir to ensure
the permissions check is examining the correct directory.
Reviewed-by: Daniel Gomez <da.gomez@samsung.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
kconfigs/Kconfig.guestfs | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kconfigs/Kconfig.guestfs b/kconfigs/Kconfig.guestfs
index d309436fa7c9..460ee703fd68 100644
--- a/kconfigs/Kconfig.guestfs
+++ b/kconfigs/Kconfig.guestfs
@@ -8,7 +8,7 @@ config STORAGE_POOL_PATH
config GUESTFS_STORAGE_DIR
string
output yaml
- default "{{ kdevops_storage_pool_path }}/kdevops/guestfs"
+ default "{{ kdevops_storage_pool_path }}/guestfs"
config GUESTFS_BASE_IMAGE_DIR
string
--
2.49.0
next prev parent reply other threads:[~2025-04-14 17:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 17:05 [PATCH v2 0/4] Add uniquifier to storage pool path cel
2025-04-14 17:05 ` cel [this message]
2025-04-23 6:36 ` [PATCH v2 1/4] guestfs: Fix definition of guestfs_storage_dir Luis Chamberlain
2025-04-14 17:05 ` [PATCH v2 2/4] install_vagrant: Remove this role cel
2025-04-23 6:23 ` Luis Chamberlain
2025-04-14 17:05 ` [PATCH v2 3/4] Replace STORAGE_POOL_PATH with LIBVIRT_STORAGE_POOL_PATH cel
2025-04-23 6:37 ` Luis Chamberlain
2025-04-14 17:05 ` [PATCH v2 4/4] guestfs: Per-user storage pools cel
2025-04-14 21:08 ` Chuck Lever
2025-04-23 6:22 ` [PATCH v2 0/4] Add uniquifier to storage pool path Luis Chamberlain
2025-04-23 6:42 ` Luis Chamberlain
2025-04-23 14:01 ` Chuck Lever
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=20250414170546.1995982-2-cel@kernel.org \
--to=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=da.gomez@samsung.com \
--cc=kdevops@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.