mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vincent Mailhol <mailhol@kernel.org>
To: Celeste Liu <uwu@coelacanthus.name>,
	Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Maximilian Schneider <max@schneidersoft.net>,
	Henrik Brix Andersen <henrik@brixandersen.dk>,
	Wolfgang Grandegger <wg@grandegger.com>,
	linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
	Runcheng Lu <runcheng.lu@hpmicro.com>
Subject: Re: [PATCH] net/can/gs_usb: increase max interface to 255
Date: Mon, 29 Sep 2025 23:52:41 +0900	[thread overview]
Message-ID: <69a0a8fa-854c-4498-a0cb-6176d8d7dd98@kernel.org> (raw)
In-Reply-To: <20250929-gs-usb-max-if-v1-1-e41b5c09133a@coelacanthus.name>

Hi Celeste,

Thank you for your patch. Here are my comments.

On 9/29/25 8:10 PM, Celeste Liu wrote:
> This issue was found by Runcheng Lu when develop HSCanT USB to CAN FD
> converter[1]. The original developers may have only 3 intefaces device to
> test so they write 3 here and wait for future change.
> 
> During the HSCanT development, we actually used 4 interfaces, so the
> limitation of 3 is not enough now. But just increase one is not
> future-proofed. Since the channel type in gs_host_frame is u8, use 255
> as max interface number should be safe.
> 
> [1]: https://github.com/cherry-embedded/HSCanT-hardware
> 
> Reported-by: Runcheng Lu <runcheng.lu@hpmicro.com>

If you have any links where Runcheng reported the issue, you can add it here as:

  Closes: <URL to the bug report>

(Ignore if such message does not exist).

Also add a Fixes tag so that the fix can be backported to stable.

> Signed-off-by: Celeste Liu <uwu@coelacanthus.name>
> ---
>  drivers/net/can/usb/gs_usb.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/can/usb/gs_usb.c b/drivers/net/can/usb/gs_usb.c
> index c9482d6e947b0c7b033dc4f0c35f5b111e1bfd92..35fc257c19e57c1f33e03e7c86ea908d22400254 100644
> --- a/drivers/net/can/usb/gs_usb.c
> +++ b/drivers/net/can/usb/gs_usb.c
> @@ -290,9 +290,9 @@ struct gs_host_frame {
>  #define GS_NAPI_WEIGHT 32
>  
>  /* Maximum number of interfaces the driver supports per device.
> - * Current hardware only supports 3 interfaces. The future may vary.
> + * The channel number type of gs_host_frame is u8, so max interfaces can be 255.
>   */
> -#define GS_MAX_INTF 3
> +#define GS_MAX_INTF 255

After doing this, you are left with an array of 255 pointers in struct gs_usb
(which represents 2 kilobytes of memory on a 64 bits machine). You also have two
loops iterating from 0 to 255. This is a bit of a waste of both space and
processing power.

It is better to use a flexible array member, like this:

-----8<-----
diff --git a/drivers/net/can/usb/gs_usb.c b/drivers/net/can/usb/gs_usb.c
index c9482d6e947b..459a956ac0d9 100644
--- a/drivers/net/can/usb/gs_usb.c
+++ b/drivers/net/can/usb/gs_usb.c
@@ -324,7 +324,6 @@ struct gs_can {

 /* usb interface struct */
 struct gs_usb {
-       struct gs_can *canch[GS_MAX_INTF];
        struct usb_anchor rx_submitted;
        struct usb_device *udev;

@@ -336,9 +335,11 @@ struct gs_usb {

        unsigned int hf_size_rx;
        u8 active_channels;
+       u8 channel_cnt;

        unsigned int pipe_in;
        unsigned int pipe_out;
+       struct gs_can *canch[] __counted_by(channel_cnt);
 };

 /* 'allocate' a tx context.
----->8-----

Then all the instances of GS_MAX_INTF are replaced by gs_usb->channel_cnt except
from the check on dfconf.icount which can be replaced by a:

  type_max(typeof(gs_usb->channel_cnt))


Yours sincerely,
Vincent Mailhol


  reply	other threads:[~2025-09-30  1:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 11:10 Celeste Liu
2025-09-29 14:52 ` Vincent Mailhol [this message]
2025-09-30  3:03   ` Celeste Liu

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=69a0a8fa-854c-4498-a0cb-6176d8d7dd98@kernel.org \
    --to=mailhol@kernel.org \
    --cc=henrik@brixandersen.dk \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@schneidersoft.net \
    --cc=mkl@pengutronix.de \
    --cc=runcheng.lu@hpmicro.com \
    --cc=uwu@coelacanthus.name \
    --cc=wg@grandegger.com \
    /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

all inboxes | Powered by JetHome®