From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Sebastian Ott <sebott@linux.vnet.ibm.com>
Cc: Yishai Hadas <yishaih@mellanox.com>,
Tariq Toukan <tariqt@mellanox.com>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/mlx4_en: fix off by one in error handling
Date: Wed, 14 Sep 2016 17:49:49 +0300 [thread overview]
Message-ID: <b2197c51-57a9-ab01-e940-9850a39484d6@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1609141548390.11022@schleppi>
On 14/09/2016 4:53 PM, Sebastian Ott wrote:
> Hello Tariq,
>
> On Wed, 14 Sep 2016, Tariq Toukan wrote:
>> On 14/09/2016 2:09 PM, Sebastian Ott wrote:
>>> If an error occurs in mlx4_init_eq_table the index used in the
>>> err_out_unmap label is one too big which results in a panic in
>>> mlx4_free_eq. This patch fixes the index in the error path.
>> You are right, but your change below does not cover all cases.
>> The full solution looks like this:
>>
>> @@ -1260,7 +1260,7 @@ int mlx4_init_eq_table(struct mlx4_dev *dev)
>> eq);
>> }
>> if (err)
>> - goto err_out_unmap;
>> + goto err_out_unmap_excluded;
> In this case a call to mlx4_create_eq failed. Do you really have to call
> mlx4_free_eq for this index again?
We agree on this part, that's why here we should goto the _excluded_ label.
For all other parts, we should not exclude the eq in the highest index,
and thus we goto the _non_excluded_ label.
> As far as I understood this code
> mlx4_create_eq cleans up when it fails and thus there is no need for an
> additional mlx4_free_eq call.
>
> Regards,
> Sebastian
>
Regards,
Tariq
next prev parent reply other threads:[~2016-09-14 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 11:09 [PATCH] net/mlx4_en: fix off by one in error handling Sebastian Ott
2016-09-14 13:43 ` Tariq Toukan
[not found] ` <df5834ee-00c2-3f18-ae83-8bb06b6c675b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-09-14 13:53 ` Sebastian Ott
2016-09-14 14:49 ` Tariq Toukan [this message]
2016-09-14 16:08 ` Sebastian Ott
2016-09-15 12:18 ` Tariq Toukan
2016-09-16 8:16 ` David Miller
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=b2197c51-57a9-ab01-e940-9850a39484d6@gmail.com \
--to=ttoukan.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sebott@linux.vnet.ibm.com \
--cc=tariqt@mellanox.com \
--cc=yishaih@mellanox.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).