diff options
| author | Brian Silverman <brian.silverman@bluerivertech.com> | 2022-01-05 16:29:50 -0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-01-27 09:04:12 +0100 |
| commit | 6332e925ee257e2362be5a6943b9e85b138a2fe9 (patch) | |
| tree | 6f238db3e5dfd7a5eb20eaba5182f07cad64795e /drivers/char | |
| parent | 359cd38937e290cd5d24857061e081ce68f61992 (diff) | |
| download | linux-stable-6332e925ee257e2362be5a6943b9e85b138a2fe9.tar.gz linux-stable-6332e925ee257e2362be5a6943b9e85b138a2fe9.tar.bz2 linux-stable-6332e925ee257e2362be5a6943b9e85b138a2fe9.zip | |
can: gs_usb: gs_can_start_xmit(): zero-initialize hf->{flags,reserved}
commit 89d58aebe14a365c25ba6645414afdbf4e41cea4 upstream.
No information is deliberately sent in hf->flags in host -> device
communications, but the open-source candleLight firmware echoes it
back, which can result in the GS_CAN_FLAG_OVERFLOW flag being set and
generating spurious ERRORFRAMEs.
While there also initialize the reserved member with 0.
Fixes: d08e973a77d1 ("can: gs_usb: Added support for the GS_USB CAN devices")
Link: https://lore.kernel.org/all/20220106002952.25883-1-brian.silverman@bluerivertech.com
Link: https://github.com/candle-usb/candleLight_fw/issues/87
Cc: stable@vger.kernel.org
Signed-off-by: Brian Silverman <brian.silverman@bluerivertech.com>
[mkl: initialize the reserved member, too]
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/char')
0 files changed, 0 insertions, 0 deletions