From: Pavel Skripkin <paskripkin@gmail.com>
To: wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net,
socketcan@hartkopp.net, mailhol.vincent@wanadoo.fr,
b.krumboeck@gmail.com, haas@ems-wuensche.com,
Stefan.Maetje@esd.eu, matthias.fuchs@esd.eu
Cc: linux-can@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] can: fix same memory leaks in can drivers
Date: Mon, 26 Jul 2021 20:29:16 +0300 [thread overview]
Message-ID: <20210726202916.5945e3d9@gmail.com> (raw)
In-Reply-To: <cover.1627311383.git.paskripkin@gmail.com>
On Mon, 26 Jul 2021 18:29:38 +0300
Pavel Skripkin <paskripkin@gmail.com> wrote:
> Hi, Marc and can drivers maintainers/reviewers!
>
I reread this I found out, that I missed logic here.
I mean:
> 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.
>
> [1]
> https://syzkaller.appspot.com/bug?id=c94c1c23e829d5ac97995d51219f0c5a0cd1fa54
> [2]
> https://lore.kernel.org/netdev/20210725103630.23864-1-paskripkin@gmail.com/
>
>
> With regards,
> Pavel Skripkin
>
> Pavel Skripkin (3):
> can: usb_8dev: fix memory leak
> can: ems_usb: fix memory leak
> can: esd_usb2: fix memory leak
>
> drivers/net/can/usb/ems_usb.c | 14 +++++++++++++-
> drivers/net/can/usb/esd_usb2.c | 16 +++++++++++++++-
> drivers/net/can/usb/usb_8dev.c | 15 +++++++++++++--
> 3 files changed, 41 insertions(+), 4 deletions(-)
>
With regards,
Pavel Skripkin
next prev parent reply other threads:[~2021-07-26 17:29 UTC|newest]
Thread overview: 13+ 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-28 20:38 ` kernel test robot
2021-07-26 17:29 ` Pavel Skripkin [this message]
2021-07-26 20:02 ` [PATCH 0/3] can: fix same memory leaks in can drivers 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 ` [PATCH v2 0/3] can: fix same memory leaks in can drivers Marc Kleine-Budde
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=20210726202916.5945e3d9@gmail.com \
--to=paskripkin@gmail.com \
--cc=Stefan.Maetje@esd.eu \
--cc=b.krumboeck@gmail.com \
--cc=davem@davemloft.net \
--cc=haas@ems-wuensche.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=matthias.fuchs@esd.eu \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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 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).