From: Mike Christie <michaelc@cs.wisc.edu>
To: Jean Delvare <jdelvare@suse.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
stable@kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [stable] [PATCH] [SCSI] libiscsi: fix iscsi pool error path
Date: Tue, 31 Mar 2009 01:38:09 -0500 [thread overview]
Message-ID: <49D1BA51.4@cs.wisc.edu> (raw)
In-Reply-To: <200903302134.30706.jdelvare@suse.de>
Jean Delvare wrote:
> Hi Chris,
>
> Le lundi 30 mars 2009, Chris Wright a écrit :
>> * Jean Delvare (jdelvare@suse.de) wrote:
>>> --- linux-2.6.29-rc5.orig/drivers/scsi/libiscsi.c 2009-01-29 08:27:19.000000000 +0100
>>> +++ linux-2.6.29-rc5/drivers/scsi/libiscsi.c 2009-02-16 21:19:14.000000000 +0100
>>> @@ -1944,7 +1944,7 @@ iscsi_pool_init(struct iscsi_pool *q, in
>>> num_arrays++;
>>> q->pool = kzalloc(num_arrays * max * sizeof(void*), GFP_KERNEL);
>>> if (q->pool == NULL)
>>> - goto enomem;
>>> + return -ENOMEM;
>>>
>>> q->queue = kfifo_init((void*)q->pool, max * sizeof(void*),
>>> GFP_KERNEL, NULL);
>>> @@ -1979,8 +1979,7 @@ void iscsi_pool_free(struct iscsi_pool *
>>>
>>> for (i = 0; i < q->max; i++)
>>> kfree(q->pool[i]);
>>> - if (q->pool)
>>> - kfree(q->pool);
>>> + kfree(q->pool);
>>> kfree(q->queue);
>> AFAICT, This is still broken.
>>
>> thanks,
>> -chris
>> --
>>
>> Subject: [PATCH] libiscsi: fix error path on iscsi_pool_init
>>
>> From: Chris Wright <chrisw@sous-sol.org>
>>
>> I'm not all that keen on kfifo_init returning ERR_PTR, but...
>
> Ah, I had not noticed this. Good catch!
>
Yeah, thanks Chris.
>> q->queue could be ERR_PTR(-ENOMEM) which will break unwinding
>> on error. Make iscsi_pool_free more defensive.
>>
>> Signed-off-by: Chris Wright <chrisw@sous-sol.org>
>> ---
>> diff --git a/drivers/scsi/libiscsi.c b/drivers/scsi/libiscsi.c
>> index dfaa8ad..2f4df53 100644
>> --- a/drivers/scsi/libiscsi.c
>> +++ b/drivers/scsi/libiscsi.c
>> @@ -1995,7 +1995,7 @@ iscsi_pool_init(struct iscsi_pool *q, int max, void ***items, int item_size)
>> num_arrays++;
>> q->pool = kzalloc(num_arrays * max * sizeof(void*), GFP_KERNEL);
>> if (q->pool == NULL)
>> - return -ENOMEM;
>> + goto enomem;
>>
>> q->queue = kfifo_init((void*)q->pool, max * sizeof(void*),
>> GFP_KERNEL, NULL);
>> @@ -2028,10 +2028,13 @@ void iscsi_pool_free(struct iscsi_pool *q)
>> {
>> int i;
>>
>> - for (i = 0; i < q->max; i++)
>> - kfree(q->pool[i]);
>> - kfree(q->pool);
>> - kfree(q->queue);
>> + if (q->pool) {
>> + for (i = 0; i < q->max; i++)
>> + kfree(q->pool[i]);
>> + kfree(q->pool);
>> + if (!IS_ERR(q->queue))
>> + kfree(q->queue);
>> + }
>> }
>> EXPORT_SYMBOL_GPL(iscsi_pool_free);
>
> Making the freeing of q->queue dependent on q->pool being set looks
> really weird (although it is correct at the moment. But this seems
> to be fixable in a much simpler way:
>
> ---
> drivers/scsi/libiscsi.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> --- linux-2.6.30-rc0.orig/drivers/scsi/libiscsi.c 2009-03-30 09:27:48.000000000 +0200
> +++ linux-2.6.30-rc0/drivers/scsi/libiscsi.c 2009-03-30 21:15:13.000000000 +0200
> @@ -1999,8 +1999,10 @@ iscsi_pool_init(struct iscsi_pool *q, in
>
> q->queue = kfifo_init((void*)q->pool, max * sizeof(void*),
> GFP_KERNEL, NULL);
> - if (q->queue == ERR_PTR(-ENOMEM))
> + if (q->queue == ERR_PTR(-ENOMEM)) {
> + q->queue = NULL;
> goto enomem;
> + }
>
> for (i = 0; i < max; i++) {
> q->pool[i] = kzalloc(item_size, GFP_KERNEL);
>
> With the benefit that only the error case is slowed down. In both
> cases we have a problem if q->queue contains an error value but it's
> not -ENOMEM. Apparently this can't happen today, but it doesn't feel
> right to assume this will always be true. Maybe it's the right time
> to fix this as well.
>
Yeah I agree. I will just modify the patch to check for IS_ERR(q->queue)
in there.
I will do a quick sanity test on it here then pass it on to James with
some other stuff for 2.6.30.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2009-03-31 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200903291119.42080.jdelvare@suse.de>
2009-03-30 18:44 ` [stable] [PATCH] [SCSI] libiscsi: fix iscsi pool error path Chris Wright
2009-03-30 18:49 ` [PATCH] libsrp: free kfifo struct in srp_iu_pool_free Chris Wright
2009-03-30 19:38 ` Jean Delvare
2009-03-30 19:34 ` [stable] [PATCH] [SCSI] libiscsi: fix iscsi pool error path Jean Delvare
2009-03-30 19:43 ` Chris Wright
2009-03-31 6:38 ` Mike Christie [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=49D1BA51.4@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=James.Bottomley@hansenpartnership.com \
--cc=chrisw@sous-sol.org \
--cc=jdelvare@suse.de \
--cc=linux-scsi@vger.kernel.org \
--cc=stable@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