Netdev List
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net/sonic: Fix some resource leaks in error handling paths
Date: Sat, 9 May 2020 09:28:38 +1000 (AEST)	[thread overview]
Message-ID: <alpine.LNX.2.22.394.2005090919460.8@nippy.intranet> (raw)
In-Reply-To: <20200508172557.218132-1-christophe.jaillet@wanadoo.fr>


On Fri, 8 May 2020, Christophe JAILLET wrote:

> A call to 'dma_alloc_coherent()' is hidden in 
> 'sonic_alloc_descriptors()'.
> 
> This is correctly freed in the remove function, but not in the error 
> handling path of the probe function. Fix it and add the missing 
> 'dma_free_coherent()' call.
> 
> While at it, rename a label in order to be slightly more informative and 
> split some too long lines.
> 
> This patch is similar to commit 10e3cc180e64 ("net/sonic: Fix a resource 
> leak in an error handling path in 'jazz_sonic_probe()'") which was for 
> 'jazzsonic.c'.
> 
> Suggested-by: Finn Thain <fthain@telegraphics.com.au>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>

Thanks.

Reviewed-by: Finn Thain <fthain@telegraphics.com.au>

> ---
> Only macsonic has been compile tested. I don't have the needed setup to
> compile xtsonic

I compile tested xtsonic.c. I didn't use an xtensa toolchain as there's 
probably no need: the new code already appears elsewhere in that file.

  reply	other threads:[~2020-05-08 23:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-08 17:25 [PATCH] net/sonic: Fix some resource leaks in error handling paths Christophe JAILLET
2020-05-08 23:28 ` Finn Thain [this message]
2020-05-09  0:57 ` Jakub Kicinski
2020-05-09  1:57   ` Finn Thain
2020-05-09  2:04     ` Jakub Kicinski
2020-05-09  1:54 ` Jakub Kicinski
2020-05-09 16:47   ` Christophe JAILLET
2020-05-09 18:13     ` Jakub Kicinski
2020-05-09 20:31       ` Christophe JAILLET
2020-05-09 22:42       ` Joe Perches
2020-05-09 23:32         ` David Miller
2020-05-09 23:41           ` Joe Perches
2020-05-09 23:52   ` Finn Thain
  -- strict thread matches above, loose matches on Subject: below --
2020-05-09  6:15 Markus Elfring
2020-05-09 23:45 ` Finn Thain
2020-05-10  5:30   ` Markus Elfring
2020-05-10  8:25     ` Finn Thain

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=alpine.LNX.2.22.394.2005090919460.8@nippy.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.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