From: Lee Duncan <lduncan@suse.com>
To: linux-scsi@vger.kernel.org, nab@linux-iscsi.org,
target-devel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hch@infradead.org, hare@suse.de,
agrover@redhat.com, jxm@netiant.com,
Lee Duncan <lduncan@suse.com>
Subject: [PATCHv2 0/2] target: make location of /var/targets configurable
Date: Wed, 13 Apr 2016 13:25:54 -0700 [thread overview]
Message-ID: <cover.1460577841.git.lduncan@suse.com> (raw)
These patches make the location of "/var/target" configurable,
though it still defauls to "/var/target".
This "target database directory" can only be changed
after the target_core_mod loads but before any
fabric drivers are loaded, and must be the pathname
of an existing directory.
This configuration is accomplished via the configfs
top-level target attribute "dbroot", i.e. dumping
out "/sys/kernel/config/target/dbroot" will normally
return "/var/target". Writing to this attribute
changes the loation where the kernel looks for the
target database.
The first patch creates this configurable value for
the "dbroot", and the second patch modifies users
of this directory to use this new attribute.
Changes from v1:
* Only allow changing target DB root before it
can be used by others
* Validate that new DB root is a valid directory
Lee Duncan (2):
target: make target db location configurable
target: use new "dbroot" target attribute
drivers/target/target_core_alua.c | 6 ++---
drivers/target/target_core_configfs.c | 51 +++++++++++++++++++++++++++++++++++
drivers/target/target_core_internal.h | 6 +++++
drivers/target/target_core_pr.c | 2 +-
4 files changed, 61 insertions(+), 4 deletions(-)
--
2.1.4
next reply other threads:[~2016-04-13 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 20:25 Lee Duncan [this message]
2016-04-13 20:25 ` [PATCHv2 1/2] target: make target db location configurable Lee Duncan
2016-04-14 6:10 ` Hannes Reinecke
2016-04-15 0:04 ` Lee Duncan
2016-04-13 20:25 ` [PATCH 2/2] target: use new "dbroot" target attribute Lee Duncan
2016-04-14 6:10 ` Hannes Reinecke
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=cover.1460577841.git.lduncan@suse.com \
--to=lduncan@suse.com \
--cc=agrover@redhat.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jxm@netiant.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
/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).