From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
socketcan@hartkopp.net,
syzbot+2d7f58292cb5b29eb5ad@syzkaller.appspotmail.com,
harperchen1110@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH net 1/4] can: af_can: fix NULL pointer dereference in can_rcv_filter
Date: Thu, 08 Dec 2022 03:10:16 +0000 [thread overview]
Message-ID: <167046901651.21108.4760310811680515367.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221207105243.2483884-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net.git (master)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Wed, 7 Dec 2022 11:52:40 +0100 you wrote:
> From: Oliver Hartkopp <socketcan@hartkopp.net>
>
> Analogue to commit 8aa59e355949 ("can: af_can: fix NULL pointer
> dereference in can_rx_register()") we need to check for a missing
> initialization of ml_priv in the receive path of CAN frames.
>
> Since commit 4e096a18867a ("net: introduce CAN specific pointer in the
> struct net_device") the check for dev->type to be ARPHRD_CAN is not
> sufficient anymore since bonding or tun netdevices claim to be CAN
> devices but do not initialize ml_priv accordingly.
>
> [...]
Here is the summary with links:
- [net,1/4] can: af_can: fix NULL pointer dereference in can_rcv_filter
https://git.kernel.org/netdev/net/c/0acc442309a0
- [net,2/4] can: slcan: fix freed work crash
https://git.kernel.org/netdev/net/c/fb855e9f3b6b
- [net,3/4] can: can327: flush TX_work on ldisc .close()
https://git.kernel.org/netdev/net/c/f4a4d121ebec
- [net,4/4] can: esd_usb: Allow REC and TEC to return to zero
https://git.kernel.org/netdev/net/c/918ee4911f7a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-12-08 3:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 10:52 [PATCH net 0/4] pull-request: can 2022-12-07 Marc Kleine-Budde
2022-12-07 10:52 ` [PATCH net 1/4] can: af_can: fix NULL pointer dereference in can_rcv_filter Marc Kleine-Budde
2022-12-08 3:10 ` patchwork-bot+netdevbpf [this message]
2022-12-07 10:52 ` [PATCH net 2/4] can: slcan: fix freed work crash Marc Kleine-Budde
2022-12-07 10:52 ` [PATCH net 3/4] can: can327: flush TX_work on ldisc .close() Marc Kleine-Budde
2022-12-07 10:52 ` [PATCH net 4/4] can: esd_usb: Allow REC and TEC to return to zero 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=167046901651.21108.4760310811680515367.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=harperchen1110@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=stable@vger.kernel.org \
--cc=syzbot+2d7f58292cb5b29eb5ad@syzkaller.appspotmail.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).