linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: ieatmuttonchuan@gmail.com, meissner@suse.de, mkubecek@suse.cz,
	netdev@vger.kernel.org
Subject: [PATCH 0/3] RFC/RFT: CAN FD support for can-gw
Date: Thu, 10 Jan 2019 22:02:52 +0100	[thread overview]
Message-ID: <20190110210255.4291-1-socketcan@hartkopp.net> (raw)

As a follow-up to the discussion about CVE-2019-3701 I walked through the
can-gw code to add the support for handling CAN FD frames.

Patch 1/3 is still the CVE fix and can be omitted when a recent Linux tree
is used that is already patched.

Patch 2/3 and 3/3 introduce the CAN FD support.

The updated user space tool 'cangw' can be found in the 'cangwfd' branch of
my can-utils fork at https://github.com/hartkopp/can-utils .

Feedback and testing is welcome!

Oliver Hartkopp (3):
  can: gw: ensure DLC boundaries after CAN frame modification
  can: gw: use struct canfd_frame as internal data structure
  can: gw: add support for CAN FD frames

 include/uapi/linux/can/gw.h |  17 +-
 net/can/gw.c                | 424 +++++++++++++++++++++++++++---------
 2 files changed, 333 insertions(+), 108 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-01-10 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 21:02 Oliver Hartkopp [this message]
2019-01-10 21:02 ` [PATCH 1/3] can: gw: ensure DLC boundaries after CAN frame modification Oliver Hartkopp
2019-01-10 21:02 ` [PATCH 2/3] can: gw: use struct canfd_frame as internal data structure Oliver Hartkopp
2019-01-10 21:02 ` [PATCH 3/3] can: gw: add support for CAN FD frames Oliver Hartkopp

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=20190110210255.4291-1-socketcan@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=ieatmuttonchuan@gmail.com \
    --cc=linux-can@vger.kernel.org \
    --cc=meissner@suse.de \
    --cc=mkubecek@suse.cz \
    --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).