All of lore.kernel.org
 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,
	dja@ozlabs.au.ibm.com, benh@kernel.crashing.org,
	hch@infradead.org, imunsie@au1.ibm.com
Subject: Re: [PATCH v5 3/3] cxlflash: Virtual LUN support
Date: Thu, 13 Aug 2015 20:39:19 -0500	[thread overview]
Message-ID: <55CD46C7.5060506@linux.vnet.ibm.com> (raw)
In-Reply-To: <1439514506.2641.2.camel@neuling.org>

Mikey:

Thanks for pointing this out. The patch for 2/3 should address this
issue.

Regards,
- Manoj Kumar


On 8/13/2015 8:08 PM, Michael Neuling wrote:
> On Thu, 2015-08-13 at 18:43 -0500, Manoj Kumar wrote:
>> Mikey:
>>
>> Thanks for your review. See comment inline below.
>>
>> - Manoj Kumar
>>
>> On 8/13/2015 7:03 AM, Michael Neuling wrote:
>>> Thanks for integrating my suggestions.  create_context() has the same
>>> freeing bug as 2/3 but if you fix that I'm happy if you add my
>>> reviewed by:
>>>
>>> Reviewed-by: Michael Neuling <mikey@neuling.org>
>>
>> I believe create_context() is in 2/3, not here. I did not find the same
>> issue in this patch.
>>
>
> This is the section I referring to from this patch.  Seems to be
> building on the 2/3 issue.
>
>
> @@ -693,11 +737,13 @@ static struct ctx_info *create_context(struct cxlflash_cfg *cfg,
>   	struct afu *afu = cfg->afu;
>   	struct ctx_info *ctxi = NULL;
>   	struct llun_info **lli = NULL;
> +	bool *ws = NULL;
>   	struct sisl_rht_entry *rhte;
>
>   	ctxi = kzalloc(sizeof(*ctxi), GFP_KERNEL);
>   	lli = kzalloc((MAX_RHT_PER_CONTEXT * sizeof(*lli)), GFP_KERNEL);
> -	if (unlikely(!ctxi || !lli)) {
> +	ws = kzalloc((MAX_RHT_PER_CONTEXT * sizeof(*ws)), GFP_KERNEL);
> +	if (unlikely(!ctxi || !lli || !ws)) {
>   		dev_err(dev, "%s: Unable to allocate context!\n", __func__);
>   		goto out;

This will be changed to 'goto err' by the v6 patch 2/3.




  reply	other threads:[~2015-08-14  1:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12 23:51 [PATCH v5 3/3] cxlflash: Virtual LUN support Matthew R. Ochs
2015-08-13 12:03 ` Michael Neuling
2015-08-13 23:43   ` Manoj Kumar
2015-08-14  1:08     ` Michael Neuling
2015-08-14  1:39       ` Manoj Kumar [this message]
2015-08-13 13:27 ` wenxiong

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=55CD46C7.5060506@linux.vnet.ibm.com \
    --to=manoj@linux.vnet.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=benh@kernel.crashing.org \
    --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 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.