From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: net/rxrpc/output.c:974:1: warning: the frame size of 1160 bytes is larger than 1024 bytes
Date: Tue, 24 Jun 2025 04:18:43 +0800 [thread overview]
Message-ID: <202506240423.E942yKJP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 86731a2a651e58953fc949573895f2fa6d456841
commit: 5800b1cf3fd8ccab752a101865be1e76dac33142 rxrpc: Allow CHALLENGEs to the passed to the app for a RESPONSE
date: 2 months ago
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20250624/202506240423.E942yKJP-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250624/202506240423.E942yKJP-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/202506240423.E942yKJP-lkp@intel.com/
All warnings (new ones prefixed by >>):
net/rxrpc/output.c: In function 'rxrpc_send_response':
>> net/rxrpc/output.c:974:1: warning: the frame size of 1160 bytes is larger than 1024 bytes [-Wframe-larger-than=]
974 | }
| ^
vim +974 net/rxrpc/output.c
919
920 /*
921 * Send a RESPONSE message.
922 */
923 void rxrpc_send_response(struct rxrpc_connection *conn, struct sk_buff *response)
924 {
925 struct rxrpc_skb_priv *sp = rxrpc_skb(response);
926 struct scatterlist sg[16];
927 struct bio_vec bvec[16];
928 struct msghdr msg;
929 size_t len = sp->resp.len;
930 __be32 wserial;
931 u32 serial = 0;
932 int ret, nr_sg;
933
934 _enter("C=%x,%x", conn->debug_id, sp->resp.challenge_serial);
935
936 sg_init_table(sg, ARRAY_SIZE(sg));
937 ret = skb_to_sgvec(response, sg, 0, len);
938 if (ret < 0)
939 goto fail;
940 nr_sg = ret;
941
942 for (int i = 0; i < nr_sg; i++)
943 bvec_set_page(&bvec[i], sg_page(&sg[i]), sg[i].length, sg[i].offset);
944
945 iov_iter_bvec(&msg.msg_iter, WRITE, bvec, nr_sg, len);
946
947 msg.msg_name = &conn->peer->srx.transport;
948 msg.msg_namelen = conn->peer->srx.transport_len;
949 msg.msg_control = NULL;
950 msg.msg_controllen = 0;
951 msg.msg_flags = MSG_SPLICE_PAGES;
952
953 serial = rxrpc_get_next_serials(conn, 1);
954 wserial = htonl(serial);
955
956 ret = skb_store_bits(response, offsetof(struct rxrpc_wire_header, serial),
957 &wserial, sizeof(wserial));
958 if (ret < 0)
959 goto fail;
960
961 rxrpc_local_dont_fragment(conn->local, false);
962
963 ret = do_udp_sendmsg(conn->local->socket, &msg, len);
964 if (ret < 0)
965 goto fail;
966
967 conn->peer->last_tx_at = ktime_get_seconds();
968 return;
969
970 fail:
971 trace_rxrpc_tx_fail(conn->debug_id, serial, ret,
972 rxrpc_tx_point_response);
973 kleave(" = %d", ret);
> 974 }
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-06-23 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 20:18 kernel test robot [this message]
2025-06-30 9:17 ` David Howells
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=202506240423.E942yKJP-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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®