From: Ziyang Xuan <william.xuanziyang@huawei.com>
To: <socketcan@hartkopp.net>
Cc: <mkl@pengutronix.de>, <davem@davemloft.net>, <kuba@kernel.org>,
<linux-can@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH net 0/2] fix tx buffer concurrent access protection
Date: Sun, 26 Sep 2021 19:01:07 +0800 [thread overview]
Message-ID: <cover.1632653477.git.william.xuanziyang@huawei.com> (raw)
Fix tx buffer concurrent access protection in isotp_sendmsg().
Ziyang Xuan (2):
can: isotp: add result check for wait_event_interruptible()
can: isotp: fix tx buffer concurrent access in isotp_sendmsg()
net/can/isotp.c | 46 ++++++++++++++++++++++++++++++++--------------
1 file changed, 32 insertions(+), 14 deletions(-)
--
2.25.1
next reply other threads:[~2021-09-26 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 11:01 Ziyang Xuan [this message]
2021-09-26 11:01 ` [PATCH net 1/2] can: isotp: add result check for wait_event_interruptible() Ziyang Xuan
2021-09-26 11:01 ` [PATCH net 2/2] can: isotp: fix tx buffer concurrent access in isotp_sendmsg() Ziyang Xuan
2021-09-30 5:47 ` kernel test robot
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=cover.1632653477.git.william.xuanziyang@huawei.com \
--to=william.xuanziyang@huawei.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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).