From: Lee Duncan <lduncan@suse.com>
To: linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Cc: nab@linux-iscsi.org, hch@infradead.org, lkml@vger.kernel.org,
hare@suse.com, Lee Duncan <lduncan@suse.com>
Subject: [PATCH 0/2] target: make location of /var/target configurable
Date: Thu, 31 Mar 2016 11:05:28 -0700 [thread overview]
Message-ID: <cover.1459278305.git.lduncan@suse.com> (raw)
These patches make the location of "/var/target" configurable,
though it still defauls to "/var/target".
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.
** NOTE/QUESTION: no sanity checks are done on the path passed in,
but it seems like *some* should be done. At least checking that
it's an abosolute path (i.e. starts with '/')? Opinions?
Lee Duncan (2):
Make target db location /var/targets configurable.
Use the new "dbroot" configfs target attribute.
drivers/target/target_core_alua.c | 6 +++---
drivers/target/target_core_configfs.c | 31 +++++++++++++++++++++++++++++++
drivers/target/target_core_internal.h | 6 ++++++
drivers/target/target_core_pr.c | 2 +-
4 files changed, 41 insertions(+), 4 deletions(-)
--
2.1.4
next reply other threads:[~2016-03-31 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 18:05 Lee Duncan [this message]
2016-03-31 18:05 ` [PATCH 1/2] target: Make target db location configurable Lee Duncan
2016-04-01 7:57 ` Johannes Thumshirn
2016-03-31 18:05 ` [PATCH 2/2] target: use new "dbroot" target attribute Lee Duncan
2016-04-01 7:58 ` Johannes Thumshirn
2016-04-01 18:01 ` Lee Duncan
2016-04-01 18:18 ` Andy Grover
2016-04-05 1:09 ` Lee Duncan
2016-04-03 3:36 ` [PATCH 0/2] target: make location of /var/target configurable Nicholas A. Bellinger
2016-04-05 1:15 ` Lee Duncan
2016-04-05 2:15 ` Nicholas A. Bellinger
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.1459278305.git.lduncan@suse.com \
--to=lduncan@suse.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkml@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 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.