From: kernel test robot <lkp@intel.com>
To: Lakshmi Prasanna Eachuri <lakshmi.prasanna.eachuri@amd.com>
Cc: oe-kbuild-all@lists.linux.dev, git@amd.com,
Michal Simek <monstr@monstr.eu>,
Vishal Sagar <vishal.sagar@amd.com>
Subject: [xilinx-xlnx:master 1000/1123] drivers/gpu/drm/xlnx/hdcp/xlnx_hdcp2x_crypt.c:147:1: warning: the frame size of 1536 bytes is larger than 1024 bytes
Date: Fri, 20 Oct 2023 01:41:57 +0800 [thread overview]
Message-ID: <202310200100.hbreEaMs-lkp@intel.com> (raw)
tree: https://github.com/Xilinx/linux-xlnx master
head: cb1f2dbc7e487361688257fccf78bf3f3ce0e9ed
commit: f5e31866859a5b682c6668e40f17b5f760dca9c1 [1000/1123] drm: xlnx: Add HDCP2X TX support
config: nios2-allmodconfig (https://download.01.org/0day-ci/archive/20231020/202310200100.hbreEaMs-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231020/202310200100.hbreEaMs-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/202310200100.hbreEaMs-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/gpu/drm/xlnx/hdcp/xlnx_hdcp2x_crypt.c: In function 'xlnx_hdcp2x_tx_rsa_encrypt':
>> drivers/gpu/drm/xlnx/hdcp/xlnx_hdcp2x_crypt.c:147:1: warning: the frame size of 1536 bytes is larger than 1024 bytes [-Wframe-larger-than=]
147 | }
| ^
vim +147 drivers/gpu/drm/xlnx/hdcp/xlnx_hdcp2x_crypt.c
127
128 static int xlnx_hdcp2x_tx_rsa_encrypt(const u8 *rsa_public_key, int public_key_size,
129 const u8 *exponent_key, int exponent_key_size,
130 const u8 *msg, int msg_size, u8 *encrypted_msg)
131 {
132 unsigned int n[BD_MAX_MOD_SIZE], e[BD_MAX_MOD_SIZE],
133 m[BD_MAX_MOD_SIZE], s[BD_MAX_MOD_SIZE];
134 unsigned int mod_size = public_key_size / sizeof(unsigned int);
135
136 if (msg_size != public_key_size)
137 return -EINVAL;
138
139 mp_conv_from_octets(n, mod_size, rsa_public_key, public_key_size);
140 mp_conv_from_octets(e, mod_size, exponent_key, exponent_key_size);
141
142 mp_conv_from_octets(m, mod_size, msg, msg_size);
143 mp_mod_exp(s, m, e, n, mod_size);
144 mp_conv_to_octets(s, mod_size, encrypted_msg, msg_size);
145
146 return 0;
> 147 }
148
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-19 17:42 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=202310200100.hbreEaMs-lkp@intel.com \
--to=lkp@intel.com \
--cc=git@amd.com \
--cc=lakshmi.prasanna.eachuri@amd.com \
--cc=monstr@monstr.eu \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vishal.sagar@amd.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 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.