From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, linux-can@vger.kernel.org, kernel@pengutronix.de
Subject: pull-request: can 2018-01-18
Date: Thu, 18 Jan 2018 11:15:05 +0100 [thread overview]
Message-ID: <20180118101507.17943-1-mkl@pengutronix.de> (raw)
Hello David,
this is a pull reqeust of two patches for net/master:
The syzkaller project triggered two WARN_ONCE() in the af_can code from
userspace and we decided to replace it by a pr_warn_once().
regards,
Marc
---
The following changes since commit ad9294dbc227cbc8e173b3b963e7dd9af5314f77:
bpf: fix cls_bpf on filter replace (2018-01-17 17:14:06 -0500)
are available in the Git repository at:
ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can.git tags/linux-can-fixes-for-4.15-20180118
for you to fetch changes up to d4689846881d160a4d12a514e991a740bcb5d65a:
can: af_can: canfd_rcv(): replace WARN_ONCE by pr_warn_once (2018-01-18 09:32:54 +0100)
----------------------------------------------------------------
linux-can-fixes-for-4.15-20180118
----------------------------------------------------------------
Marc Kleine-Budde (2):
can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once
can: af_can: canfd_rcv(): replace WARN_ONCE by pr_warn_once
net/can/af_can.c | 36 ++++++++++++++----------------------
1 file changed, 14 insertions(+), 22 deletions(-)
next reply other threads:[~2018-01-18 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-18 10:15 Marc Kleine-Budde [this message]
2018-01-18 10:15 ` [PATCH 1/2] can: af_can: can_rcv(): replace WARN_ONCE by pr_warn_once Marc Kleine-Budde
2018-01-18 10:15 ` [PATCH 2/2] can: af_can: canfd_rcv(): " Marc Kleine-Budde
2018-01-19 2:16 ` pull-request: can 2018-01-18 David Miller
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=20180118101507.17943-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--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).