From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Mike Christie <michaelc@cs.wisc.edu>,
Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
James Bottomley <James.Bottomley@suse.de>,
Jens Axboe <axboe@kernel.dk>, Boaz Harrosh <bharrosh@panasas.com>,
Joel Becker <joel.becker@oracle.com>
Subject: Re: [RFCv3 00/21] TCM Core and TCM_Loop patches for v2.6.37
Date: Mon, 08 Nov 2010 13:20:07 -0800 [thread overview]
Message-ID: <1289251207.27226.59.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <20101108143952.GB22121@infradead.org>
On Mon, 2010-11-08 at 09:39 -0500, Christoph Hellwig wrote:
> Some comments on the configfs to backend API:
>
> - the various get_*_info methods look like they really should use
> the seq_file API. That gives you safety against overflows,
> and simplifies the code.
Hmmm, it is my understanding that seq_file is currently not available
for configfs. Also, we never going to expect these particular calls to
return anything close to PAGE_SIZE, so I am not sure how much of an
issue this really is.
> - why are show_configfs_dev_params and get_dev_info separate
> methods if they always end up calling the same code?
Hmmm, this was some legacy informational code that no longer has a
reason to be seperate. I will get this merged into a single function.
> - the set_configfs_dev_params method implementation contains some
> rather nast parsing code. They look like they really should use
> the parser.h helpers we use for mount option parsing.
<nod> This code current expects the the incoming buffer to be in the
form of 'key0=value0,key1=value1,key2=value2' etc. Assuming that
parser.h code can handle the comma seperated values, I will look at
getting these converted as well.
--nab
next prev parent reply other threads:[~2010-11-08 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 22:35 Nicholas A. Bellinger
2010-11-08 14:33 ` Christoph Hellwig
2010-11-08 14:50 ` FUJITA Tomonori
2010-11-08 15:08 ` Christoph Hellwig
2010-11-08 21:10 ` Nicholas A. Bellinger
2010-11-08 14:39 ` Christoph Hellwig
2010-11-08 21:20 ` Nicholas A. Bellinger [this message]
2010-11-08 21:48 ` Christoph Hellwig
2010-11-08 22:04 ` Nicholas A. Bellinger
2010-11-08 22:37 ` Christoph Hellwig
2010-11-08 18:23 ` Christoph Hellwig
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=1289251207.27226.59.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@suse.de \
--cc=axboe@kernel.dk \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=joel.becker@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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
all inboxes | Powered by JetHome®