From: kernel test robot <lkp@intel.com>
To: Alex Markuze <amarkuze@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
ceph-devel@vger.kernel.org
Subject: [ceph-client:tls_logger 13/13] net/ceph/messenger_v2.c:2791:12: warning: stack frame size (9848) exceeds limit (8192) in 'process_control'
Date: Fri, 14 Feb 2025 02:29:04 +0800 [thread overview]
Message-ID: <202502140205.1AGkREJM-lkp@intel.com> (raw)
tree: https://github.com/ceph/ceph-client.git tls_logger
head: cd1e899feeb6a7da55cbb74b9245c8bbb77f82ba
commit: cd1e899feeb6a7da55cbb74b9245c8bbb77f82ba [13/13] cephsun: using a dynamic buffer allocation
config: x86_64-randconfig-005-20250213 (https://download.01.org/0day-ci/archive/20250214/202502140205.1AGkREJM-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250214/202502140205.1AGkREJM-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202502140205.1AGkREJM-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/ceph/messenger_v2.c:2791:12: warning: stack frame size (9848) exceeds limit (8192) in 'process_control' [-Wframe-larger-than]
2791 | static int process_control(struct ceph_connection *con, void *p, void *end)
| ^
1 warning generated.
--
>> net/ceph/messenger_v1.c:1326:5: warning: stack frame size (13688) exceeds limit (8192) in 'ceph_con_v1_try_read' [-Wframe-larger-than]
1326 | int ceph_con_v1_try_read(struct ceph_connection *con)
| ^
1 warning generated.
vim +/process_control +2791 net/ceph/messenger_v2.c
cd1a677cad99402 Ilya Dryomov 2020-11-19 2790
cd1a677cad99402 Ilya Dryomov 2020-11-19 @2791 static int process_control(struct ceph_connection *con, void *p, void *end)
cd1a677cad99402 Ilya Dryomov 2020-11-19 2792 {
cd1a677cad99402 Ilya Dryomov 2020-11-19 2793 int tag = con->v2.in_desc.fd_tag;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2794 int ret;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2795
cd1a677cad99402 Ilya Dryomov 2020-11-19 2796 dout("%s con %p tag %d len %d\n", __func__, con, tag, (int)(end - p));
cd1a677cad99402 Ilya Dryomov 2020-11-19 2797
cd1a677cad99402 Ilya Dryomov 2020-11-19 2798 switch (tag) {
cd1a677cad99402 Ilya Dryomov 2020-11-19 2799 case FRAME_TAG_HELLO:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2800 ret = process_hello(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2801 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2802 case FRAME_TAG_AUTH_BAD_METHOD:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2803 ret = process_auth_bad_method(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2804 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2805 case FRAME_TAG_AUTH_REPLY_MORE:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2806 ret = process_auth_reply_more(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2807 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2808 case FRAME_TAG_AUTH_DONE:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2809 ret = process_auth_done(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2810 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2811 case FRAME_TAG_AUTH_SIGNATURE:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2812 ret = process_auth_signature(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2813 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2814 case FRAME_TAG_SERVER_IDENT:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2815 ret = process_server_ident(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2816 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2817 case FRAME_TAG_IDENT_MISSING_FEATURES:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2818 ret = process_ident_missing_features(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2819 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2820 case FRAME_TAG_SESSION_RECONNECT_OK:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2821 ret = process_session_reconnect_ok(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2822 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2823 case FRAME_TAG_SESSION_RETRY:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2824 ret = process_session_retry(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2825 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2826 case FRAME_TAG_SESSION_RETRY_GLOBAL:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2827 ret = process_session_retry_global(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2828 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2829 case FRAME_TAG_SESSION_RESET:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2830 ret = process_session_reset(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2831 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2832 case FRAME_TAG_KEEPALIVE2_ACK:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2833 ret = process_keepalive2_ack(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2834 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2835 case FRAME_TAG_ACK:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2836 ret = process_ack(con, p, end);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2837 break;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2838 default:
cd1a677cad99402 Ilya Dryomov 2020-11-19 2839 pr_err("bad tag %d\n", tag);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2840 con->error_msg = "protocol error, bad tag";
cd1a677cad99402 Ilya Dryomov 2020-11-19 2841 return -EINVAL;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2842 }
cd1a677cad99402 Ilya Dryomov 2020-11-19 2843 if (ret) {
cd1a677cad99402 Ilya Dryomov 2020-11-19 2844 dout("%s con %p error %d\n", __func__, con, ret);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2845 return ret;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2846 }
cd1a677cad99402 Ilya Dryomov 2020-11-19 2847
cd1a677cad99402 Ilya Dryomov 2020-11-19 2848 prepare_read_preamble(con);
cd1a677cad99402 Ilya Dryomov 2020-11-19 2849 return 0;
cd1a677cad99402 Ilya Dryomov 2020-11-19 2850 }
cd1a677cad99402 Ilya Dryomov 2020-11-19 2851
:::::: The code at line 2791 was first introduced by commit
:::::: cd1a677cad994021b19665ed476aea63f5d54f31 libceph, ceph: implement msgr2.1 protocol (crc and secure modes)
:::::: TO: Ilya Dryomov <idryomov@gmail.com>
:::::: CC: Ilya Dryomov <idryomov@gmail.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-13 18:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202502140205.1AGkREJM-lkp@intel.com \
--to=lkp@intel.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.