linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manoj Kumar <manoj@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: "Matthew R. Ochs" <mrochs@linux.vnet.ibm.com>,
	linux-scsi@vger.kernel.org,
	James.Bottomley@HansenPartnership.com, nab@linux-iscsi.org,
	brking@linux.vnet.ibm.com, wenxiong@linux.vnet.ibm.com,
	hch@infradead.org, imunsie@au1.ibm.com, dja@ozlabs.au.ibm.com
Subject: Re: [PATCH v4 3/3] cxlflash: Virtual LUN support
Date: Wed, 12 Aug 2015 15:00:54 -0500	[thread overview]
Message-ID: <55CBA5F6.8060603@linux.vnet.ibm.com> (raw)
In-Reply-To: <1439349851.28873.48.camel@neuling.org>

Mikey:

Comments inline below.

- Manoj Kumar

On 8/11/2015 10:24 PM, Michael Neuling wrote:

>> The ioctls have a standard header structure, with version etc. that are
>> sanity checked before we get here. The other fields are sanity checked
>> where they are used, i.e. in get_context().
>
> That was my point.  Let's do it upfront so it's clear they've been
> checked.

Thanks for clarifying. We are going to sanity check the common header
portions up front. The others that are specific to the ioctl, will be
checked prior to use in each ioctl handler.


>>> Virt has not been sanity checked.  So now resize can contain bad data.
>>>
>>>
>>>> +	resize.rsrc_handle = rsrc_handle;
>>
>> Same as above. As mentioned earlier, the size is immaterial. The rest of
>> the parameters are set here (rsrc_handle).
>
> Humm.
>

Same as above.

>>>> +#define LXT_LUNIDX_SHIFT  8	/* LXT entry, shift for LUN index */
>>>> +#define LXT_PERM_SHIFT    4	/* LXT entry, shift for permission bits */
>>>
>>> What is LXT?
>>
>> LXT = lun translation table. There is one LXT entry per set of
>> contiguous blocks for a virtual LUN (known both to the host and to the
>> AFU). Will clarify this with inline comments.
>
> Please document this acronym before using it.

Good point. Will add a comment clarifying what an LXT is.




      reply	other threads:[~2015-08-12 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 17:09 [PATCH v4 3/3] cxlflash: Virtual LUN support Matthew R. Ochs
2015-08-11 10:54 ` Michael Neuling
2015-08-11 22:06   ` Manoj Kumar
2015-08-12  3:24     ` Michael Neuling
2015-08-12 20:00       ` Manoj Kumar [this message]

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=55CBA5F6.8060603@linux.vnet.ibm.com \
    --to=manoj@linux.vnet.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=dja@ozlabs.au.ibm.com \
    --cc=hch@infradead.org \
    --cc=imunsie@au1.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mikey@neuling.org \
    --cc=mrochs@linux.vnet.ibm.com \
    --cc=nab@linux-iscsi.org \
    --cc=wenxiong@linux.vnet.ibm.com \
    /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).