* [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch
@ 2026-08-24 8:27 PS10 PETER HONG 洪繼澤
2026-08-24 9:08 ` Greg KH
0 siblings, 1 reply; 5+ messages in thread
From: PS10 PETER HONG 洪繼澤 @ 2026-08-24 8:27 UTC (permalink / raw)
To: mkl, mailhol, gregkh; +Cc: linux-can, linux-kernel, admin, Ji-Ze Hong, stable
The struct f81604_int_data defines 9 bytes of interrupt data:
- Byte 0: Status register (sr)
- Byte 1: Interrupt register (isrc)
- Byte 2: Interrupt enable register (ier)
- Byte 3: Arbitration lost capture (alc)
- Byte 4: Error code capture (ecc)
- Byte 5: Error warning limit register (ewlr)
- Byte 6: RX error counter (rxerr)
- Byte 7: TX error counter (txerr)
- Byte 8: Reserved (val)
The hardware sends exactly 9 bytes for the interrupt endpoint.
However, the struct was defined with __aligned(4) attribute which
caused the compiler to pad the struct to 12 bytes.
This causes a problem in f81604_read_int_callback() where the short
URB check compares urb->actual_length against sizeof(*data). When
sizeof(struct f81604_int_data) is 12 but the hardware only sends 9
bytes, the check fails and valid interrupt messages are discarded.
This results in the driver only being able to transmit once because
the TX complete interrupt is never processed.
Fix this by removing the __aligned(4) attribute so the struct size
matches the actual hardware data size of 9 bytes.
Fixes: 88da17436973 ("can: usb: f81604: add Fintek F81604 support")
Fixes: 7299b1b39a25 ("can: usb: f81604: handle short interrupt urb messages properly")
Cc: stable@vger.kernel.org
Signed-off-by: Ji-Ze Hong (Peter Hong) <peter_hong@fintek.com.tw>
---
drivers/net/can/usb/f81604.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/can/usb/f81604.c b/drivers/net/can/usb/f81604.c
index f12318268e46..4c147b9d6d69 100644
--- a/drivers/net/can/usb/f81604.c
+++ b/drivers/net/can/usb/f81604.c
@@ -169,7 +169,7 @@ struct f81604_int_data {
u8 rxerr;
u8 txerr;
u8 val;
-} __packed __aligned(4);
+} __packed;
struct f81604_sff {
__be16 id;
--
2.43.0
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch
2026-08-24 8:27 [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch PS10 PETER HONG 洪繼澤
@ 2026-08-24 9:08 ` Greg KH
2026-08-24 9:14 ` Dynetrex, Admin
[not found] ` <8b816ee1-a81c-4d5d-a908-97e8640b07d2@fintek.com.tw>
0 siblings, 2 replies; 5+ messages in thread
From: Greg KH @ 2026-08-24 9:08 UTC (permalink / raw)
To: PS10 PETER HONG 洪繼澤
Cc: mkl, mailhol, linux-can, linux-kernel, admin, stable
On Mon, Aug 24, 2026 at 04:27:58PM +0800, PS10 PETER HONG 洪繼澤 wrote:
> The struct f81604_int_data defines 9 bytes of interrupt data:
> - Byte 0: Status register (sr)
> - Byte 1: Interrupt register (isrc)
> - Byte 2: Interrupt enable register (ier)
> - Byte 3: Arbitration lost capture (alc)
> - Byte 4: Error code capture (ecc)
> - Byte 5: Error warning limit register (ewlr)
> - Byte 6: RX error counter (rxerr)
> - Byte 7: TX error counter (txerr)
> - Byte 8: Reserved (val)
>
> The hardware sends exactly 9 bytes for the interrupt endpoint.
> However, the struct was defined with __aligned(4) attribute which
> caused the compiler to pad the struct to 12 bytes.
>
> This causes a problem in f81604_read_int_callback() where the short
> URB check compares urb->actual_length against sizeof(*data). When
> sizeof(struct f81604_int_data) is 12 but the hardware only sends 9
> bytes, the check fails and valid interrupt messages are discarded.
>
> This results in the driver only being able to transmit once because
> the TX complete interrupt is never processed.
>
> Fix this by removing the __aligned(4) attribute so the struct size
> matches the actual hardware data size of 9 bytes.
>
> Fixes: 88da17436973 ("can: usb: f81604: add Fintek F81604 support")
> Fixes: 7299b1b39a25 ("can: usb: f81604: handle short interrupt urb messages properly")
> Cc: stable@vger.kernel.org
> Signed-off-by: Ji-Ze Hong (Peter Hong) <peter_hong@fintek.com.tw>
Nit, doesn't match the From: line :(
Also, the first Fixes: tag isn't correct, it's the second one that
matters.
And wasn't this reported by someone already:
https://lore.kernel.org/r/A3834A07-5639-4779-844F-C5843DFC3928@dynetrex.com
?
And yes, this patch does look correct.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch
2026-08-24 9:08 ` Greg KH
@ 2026-08-24 9:14 ` Dynetrex, Admin
2026-08-24 9:38 ` Greg KH
[not found] ` <8b816ee1-a81c-4d5d-a908-97e8640b07d2@fintek.com.tw>
1 sibling, 1 reply; 5+ messages in thread
From: Dynetrex, Admin @ 2026-08-24 9:14 UTC (permalink / raw)
To: Greg KH
Cc: PS10 PETER HONG 洪繼澤,
mkl, mailhol, linux-can, linux-kernel, stable
Hey Greg,
This issue was reported by me about a month and a half ago, however, I did not have an environment setup for kernel development in order to submit a patch.
I appreciate Peter taking a look at this.
Kind Regards,
Alex
> On Aug 24, 2026, at 2:08 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
>
> On Mon, Aug 24, 2026 at 04:27:58PM +0800, PS10 PETER HONG 洪繼澤 wrote:
>> The struct f81604_int_data defines 9 bytes of interrupt data:
>> - Byte 0: Status register (sr)
>> - Byte 1: Interrupt register (isrc)
>> - Byte 2: Interrupt enable register (ier)
>> - Byte 3: Arbitration lost capture (alc)
>> - Byte 4: Error code capture (ecc)
>> - Byte 5: Error warning limit register (ewlr)
>> - Byte 6: RX error counter (rxerr)
>> - Byte 7: TX error counter (txerr)
>> - Byte 8: Reserved (val)
>>
>> The hardware sends exactly 9 bytes for the interrupt endpoint.
>> However, the struct was defined with __aligned(4) attribute which
>> caused the compiler to pad the struct to 12 bytes.
>>
>> This causes a problem in f81604_read_int_callback() where the short
>> URB check compares urb->actual_length against sizeof(*data). When
>> sizeof(struct f81604_int_data) is 12 but the hardware only sends 9
>> bytes, the check fails and valid interrupt messages are discarded.
>>
>> This results in the driver only being able to transmit once because
>> the TX complete interrupt is never processed.
>>
>> Fix this by removing the __aligned(4) attribute so the struct size
>> matches the actual hardware data size of 9 bytes.
>>
>> Fixes: 88da17436973 ("can: usb: f81604: add Fintek F81604 support")
>> Fixes: 7299b1b39a25 ("can: usb: f81604: handle short interrupt urb messages properly")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Ji-Ze Hong (Peter Hong) <peter_hong@fintek.com.tw>
>
> Nit, doesn't match the From: line :(
>
> Also, the first Fixes: tag isn't correct, it's the second one that
> matters.
>
> And wasn't this reported by someone already:
> https://lore.kernel.org/r/A3834A07-5639-4779-844F-C5843DFC3928@dynetrex.com
> ?
>
> And yes, this patch does look correct.
>
> thanks,
>
> greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch
2026-08-24 9:14 ` Dynetrex, Admin
@ 2026-08-24 9:38 ` Greg KH
0 siblings, 0 replies; 5+ messages in thread
From: Greg KH @ 2026-08-24 9:38 UTC (permalink / raw)
To: Dynetrex, Admin
Cc: PS10 PETER HONG 洪繼澤,
mkl, mailhol, linux-can, linux-kernel, stable
On Mon, Aug 24, 2026 at 02:14:26AM -0700, Dynetrex, Admin wrote:
> Hey Greg,
>
> This issue was reported by me about a month and a half ago, however, I did not have an environment setup for kernel development in order to submit a patch.
Great, a reported-by: line would be great to have added here to capture
that.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <8b816ee1-a81c-4d5d-a908-97e8640b07d2@fintek.com.tw>]
* Re: [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch
[not found] ` <8b816ee1-a81c-4d5d-a908-97e8640b07d2@fintek.com.tw>
@ 2026-08-24 10:02 ` Marc Kleine-Budde
0 siblings, 0 replies; 5+ messages in thread
From: Marc Kleine-Budde @ 2026-08-24 10:02 UTC (permalink / raw)
To: PS10 PETER HONG 洪繼澤
Cc: Greg KH, mailhol, linux-can, linux-kernel, admin, stable
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
On 24.08.2026 17:38:23, PS10 PETER HONG 洪繼澤 wrote:
> Greg KH 於 2026/8/24 下午 05:08 寫道:
> > On Mon, Aug 24, 2026 at 04:27:58PM +0800, PS10 PETER HONG 洪繼澤 wrote:
> >
> > Fixes: 88da17436973 ("can: usb: f81604: add Fintek F81604 support")
> > Fixes: 7299b1b39a25 ("can: usb: f81604: handle short interrupt urb messages properly")
> > Cc:stable@vger.kernel.org
> > Signed-off-by: Ji-Ze Hong (Peter Hong)<peter_hong@fintek.com.tw>
> > Nit, doesn't match the From: line :(
>
> Sorry, our company recently changed mail system, which now overrides
> the display name with the internal name.
>
> Could I resend the patch with the internal name in the Signed-off-by: line?
You can use the b4 "web submission" instead? It bypasses any mail system
completely.
| https://b4.docs.kernel.org/en/latest/contributor/send.html
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung Nürnberg | Phone: +49-5121-206917-129 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-08-24 10:07 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-08-24 8:27 [PATCH] can: usb: f81604: fix struct f81604_int_data size mismatch PS10 PETER HONG 洪繼澤
2026-08-24 9:08 ` Greg KH
2026-08-24 9:14 ` Dynetrex, Admin
2026-08-24 9:38 ` Greg KH
[not found] ` <8b816ee1-a81c-4d5d-a908-97e8640b07d2@fintek.com.tw>
2026-08-24 10:02 ` Marc Kleine-Budde
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®