From: Zhu Lingshan <lszhu@suse.com>
To: Lee Duncan <lduncan@suse.com>,
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
Subject: Re: [PATCHv3 0/2] target: make location of /var/targets configurable
Date: Wed, 25 May 2016 16:01:40 +0800 [thread overview]
Message-ID: <57455BE4.9060503@suse.com> (raw)
In-Reply-To: <572FE52C.2030806@suse.com>
Hi experts,
I think these patches are great, and I am ready to help in user space.
Thanks,
BR
Zhu Lingshan
On 05/09/2016 09:17 AM, Lee Duncan wrote:
> On 04/14/2016 06:18 PM, Lee Duncan wrote:
>> 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 v2:
>> * Add locking around access to target driver list
>>
>> 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 | 62 +++++++++++++++++++++++++++++++++++
>> drivers/target/target_core_internal.h | 6 ++++
>> drivers/target/target_core_pr.c | 2 +-
>> 4 files changed, 72 insertions(+), 4 deletions(-)
>>
> Ping?
next prev parent reply other threads:[~2016-05-25 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 1:18 [PATCHv3 0/2] target: make location of /var/targets configurable Lee Duncan
2016-04-15 1:18 ` [PATCHv3 1/2] target: make target db location configurable Lee Duncan
2016-04-15 1:18 ` [PATCHv3 2/2] target: use new "dbroot" target attribute Lee Duncan
2016-05-09 1:17 ` [PATCHv3 0/2] target: make location of /var/targets configurable Lee Duncan
2016-05-25 8:01 ` Zhu Lingshan [this message]
2016-06-09 23:51 ` Lee Duncan
2016-06-10 4:41 ` 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=57455BE4.9060503@suse.com \
--to=lszhu@suse.com \
--cc=agrover@redhat.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jxm@netiant.com \
--cc=lduncan@suse.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