All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: wg@grandegger.com, davem@davemloft.net, kuba@kernel.org,
	mailhol.vincent@wanadoo.fr, socketcan@hartkopp.net,
	b.krumboeck@gmail.com, haas@ems-wuensche.com,
	Stefan.Maetje@esd.eu, linux-can@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] can: fix same memory leaks in can drivers
Date: Wed, 28 Jul 2021 09:56:02 +0200	[thread overview]
Message-ID: <20210728075602.egmaxiqlkch6ujvj@pengutronix.de> (raw)
In-Reply-To: <cover.1627404470.git.paskripkin@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]

On 27.07.2021 19:59:12, Pavel Skripkin wrote:
> Hi, Marc and can drivers maintainers/reviewers!
> 
> A long time ago syzbot reported memory leak in mcba_usb can driver[1]. It was
> using strange pattern for allocating coherent buffers, which was leading to
> memory leaks. I fixed this wrong pattern in mcba_usb driver and yesterday I got
> a report, that mcba_usb stopped working since my commit. I came up with quick fix
> and all started working well.
> 
> There are at least 3 more drivers with this pattern, I decided to fix leaks
> in them too, since code is actually the same (I guess, driver authors just copy pasted
> code parts). Each of following patches is combination of 91c02557174b
> ("can: mcba_usb: fix memory leak in mcba_usb") and my yesterday fix [2].
> 
> 
> Dear maintainers/reviewers, if You have one of these hardware pieces, please, test
> these patches and report any errors you will find.

Added to linux-can-next/testing.

Marc

-- 
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2021-07-28  7:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-26 15:29 [PATCH 0/3] can: fix same memory leaks in can drivers Pavel Skripkin
2021-07-26 15:30 ` [PATCH 1/3] can: usb_8dev: fix memory leak Pavel Skripkin
2021-07-26 15:30 ` [PATCH 2/3] can: ems_usb: " Pavel Skripkin
2021-07-26 15:31 ` [PATCH 3/3] can: esd_usb2: " Pavel Skripkin
2021-07-26 19:51   ` kernel test robot
2021-07-26 19:51     ` kernel test robot
2021-07-28 20:38   ` kernel test robot
2021-07-28 20:38     ` kernel test robot
2021-07-26 17:29 ` [PATCH 0/3] can: fix same memory leaks in can drivers Pavel Skripkin
2021-07-26 20:02   ` Marc Kleine-Budde
2021-07-27 16:59 ` [PATCH v2 " Pavel Skripkin
2021-07-27 16:59   ` [PATCH v2 1/3] can: usb_8dev: fix memory leak Pavel Skripkin
2021-07-27 17:00   ` [PATCH v2 2/3] can: ems_usb: " Pavel Skripkin
2021-07-27 17:00   ` [PATCH v2 3/3] can: esd_usb2: " Pavel Skripkin
2021-07-28  7:56   ` Marc Kleine-Budde [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=20210728075602.egmaxiqlkch6ujvj@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=Stefan.Maetje@esd.eu \
    --cc=b.krumboeck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=haas@ems-wuensche.com \
    --cc=kuba@kernel.org \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mailhol.vincent@wanadoo.fr \
    --cc=netdev@vger.kernel.org \
    --cc=paskripkin@gmail.com \
    --cc=socketcan@hartkopp.net \
    --cc=wg@grandegger.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.