From: Jiri Slaby <jirislaby@kernel.org>
To: Chaitanya Vadrevu <chaitanya.vadrevu@emerson.com>,
gregkh@linuxfoundation.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>,
Jason Smith <jason.smith@emerson.com>,
Gratian Crisan <gratian.crisan@emerson.com>
Subject: Re: [PATCH] serial: 8250_ni: Fix build warning
Date: Fri, 11 Jul 2025 07:03:56 +0200 [thread overview]
Message-ID: <f84c2ee3-77b4-41c4-8517-26dfb44a2276@kernel.org> (raw)
In-Reply-To: <20250710223838.2657261-1-chaitanya.vadrevu@emerson.com>
On 11. 07. 25, 0:38, Chaitanya Vadrevu wrote:
> Allocate memory on heap instead of stack to fix following warning that
> clang version 20.1.2 produces on W=1 build.
>
> drivers/tty/serial/8250/8250_ni.c:277:12: warning: stack frame size (1072) exceeds limit (1024) in 'ni16550_probe' [-Wframe-larger-than]
Hmm, OK:
$ pahole -sy uart_8250_port drivers/tty/serial/8250/8250_port.o
uart_8250_port 784 4
That's quite a few. I am not sure why we did not see this earlier?
Perhaps because CONFIG_FRAME_WARN is set higher for most use/compilation
cases.
Should we switch all probes?
I have a patchset to move ops to a separate struct (pointer), but that's
far from finished and it does not save that much:
uart_8250_port 624 4
Another question is if we can introduce some lightweight struct for
register instead of full uart_8250_port which is copied from (and only
small part of it).
So perhaps:
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-07-11 5:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 22:38 Chaitanya Vadrevu
2025-07-11 5:03 ` Jiri Slaby [this message]
2025-07-11 5:50 ` Greg KH
2025-07-11 19:27 ` Chaitanya Vadrevu
2025-07-12 6:47 ` Greg KH
2025-07-12 6:49 ` Greg KH
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=f84c2ee3-77b4-41c4-8517-26dfb44a2276@kernel.org \
--to=jirislaby@kernel.org \
--cc=chaitanya.vadrevu@emerson.com \
--cc=gratian.crisan@emerson.com \
--cc=gregkh@linuxfoundation.org \
--cc=jason.smith@emerson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.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®