From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de
Subject: pull-request: can 2021-01-13
Date: Wed, 13 Jan 2021 22:21:56 +0100 [thread overview]
Message-ID: <20210113212158.925513-1-mkl@pengutronix.de> (raw)
Hello Jakub, hello David,
this is a pull request of 2 patches for net/master.
The first patch is by Oliver Hartkopp for the CAn ISO-TP protocol and fixes a
kernel information leak to userspace.
The last patch is by Qinglang Miao for the mcp251xfd driver and fixes a NULL
pointer check to work on the correct variable.
regards,
Marc
---
The following changes since commit a95d25dd7b94a5ba18246da09b4218f132fed60e:
rxrpc: Call state should be read with READ_ONCE() under some circumstances (2021-01-13 10:38:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-5.11-20210113
for you to fetch changes up to ca4c6ebeeb50112f5178f14bfb6d9e8ddf148545:
can: mcp251xfd: mcp251xfd_handle_rxif_one(): fix wrong NULL pointer check (2021-01-13 22:16:16 +0100)
----------------------------------------------------------------
linux-can-fixes-for-5.11-20210113
----------------------------------------------------------------
Oliver Hartkopp (1):
can: isotp: isotp_getname(): fix kernel information leak
Qinglang Miao (1):
can: mcp251xfd: mcp251xfd_handle_rxif_one(): fix wrong NULL pointer check
drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c | 2 +-
net/can/isotp.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
next reply other threads:[~2021-01-14 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 21:21 Marc Kleine-Budde [this message]
2021-01-13 21:21 ` [net 1/2] can: isotp: isotp_getname(): fix kernel information leak Marc Kleine-Budde
2021-01-14 3:10 ` patchwork-bot+netdevbpf
2021-01-13 21:21 ` [net 2/2] can: mcp251xfd: mcp251xfd_handle_rxif_one(): fix wrong NULL pointer check 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=20210113212158.925513-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@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;
as well as URLs for NNTP newsgroup(s).