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: [PATCH net 0/1] pull-request: can 2022-04-17
Date: Sun, 17 Apr 2022 17:29:33 +0200 [thread overview]
Message-ID: <20220417152934.2696539-1-mkl@pengutronix.de> (raw)
Hello Jakub, hello David,
this is a pull request of 1 patch for net/master.
The patch is by Oliver Hartkopp and fixes a timeout monitoring problem
in the ISO TP protocol found by the syzbot.
regards,
Marc
---
The following changes since commit 49aefd131739df552f83c566d0665744c30b1d70:
bonding: do not discard lowest hash bit for non layer3+4 hashing (2022-04-17 13:34:01 +0100)
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.18-20220417
for you to fetch changes up to d73497081710c876c3c61444445512989e102152:
can: isotp: stop timeout monitoring when no first frame was sent (2022-04-17 17:21:22 +0200)
----------------------------------------------------------------
linux-can-fixes-for-5.18-20220417
----------------------------------------------------------------
Oliver Hartkopp (1):
can: isotp: stop timeout monitoring when no first frame was sent
net/can/isotp.c | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
next reply other threads:[~2022-04-17 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 15:29 Marc Kleine-Budde [this message]
2022-04-17 15:29 ` [PATCH net] can: isotp: stop timeout monitoring when no first frame was sent Marc Kleine-Budde
2022-04-18 9:30 ` patchwork-bot+netdevbpf
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=20220417152934.2696539-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).