[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220331084223.5d145b23@kernel.org>
Date: Thu, 31 Mar 2022 08:42:23 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: netdev@...r.kernel.org, davem@...emloft.net,
linux-can@...r.kernel.org, kernel@...gutronix.de
Subject: Re: [PATCH net 0/n] pull-request: can 2022-03-31
On Thu, 31 Mar 2022 10:46:26 +0200 Marc Kleine-Budde wrote:
> The first patch is by Oliver Hartkopp and fixes MSG_PEEK feature in
> the CAN ISOTP protocol (broken in net-next for v5.18 only).
>
> Tom Rix's patch for the mcp251xfd driver fixes the propagation of an
> error value in case of an error.
>
> A patch by me for the m_can driver fixes a use-after-free in the xmit
> handler for m_can IP cores v3.0.x.
>
> Hangyu Hua contributes 3 patches fixing the same double free in the
> error path of the xmit handler in the ems_usb, usb_8dev and mcba_usb
> USB CAN driver.
>
> Pavel Skripkin contributes a patch for the mcba_usb driver to properly
> check the endpoint type.
>
> The last patch is by me and fixes a mem leak in the gs_usb, which was
> introduced in net-next for v5.18.
I think patchwork did not like the "0/n" in the subject :(
Powered by blists - more mailing lists