From: kernel test robot <lkp@intel.com>
To: Vishnu Sanal T <t.v.s10123@gmail.com>, linux-pm@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, trenn@suse.com, shuah@kernel.org,
jwyatt@redhat.com, jkacur@redhat.com,
linux-kernel@vger.kernel.org,
Vishnu Sanal T <t.v.s10123@gmail.com>
Subject: Re: [PATCH v2] implement set_enabled functions on powercap.c
Date: Mon, 4 Nov 2024 00:27:04 +0800 [thread overview]
Message-ID: <202411040029.mXFFVJ8w-lkp@intel.com> (raw)
In-Reply-To: <20241030152706.179779-2-t.v.s10123@gmail.com>
Hi Vishnu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on amd-pstate/linux-next]
[also build test WARNING on amd-pstate/bleeding-edge linus/master v6.12-rc5 next-20241101]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Vishnu-Sanal-T/implement-set_enabled-functions-on-powercap-c/20241030-233021
base: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git linux-next
patch link: https://lore.kernel.org/r/20241030152706.179779-2-t.v.s10123%40gmail.com
patch subject: [PATCH v2] implement set_enabled functions on powercap.c
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241104/202411040029.mXFFVJ8w-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/202411040029.mXFFVJ8w-lkp@intel.com/
All warnings (new ones prefixed by >>):
lib/powercap.c: In function 'powercap_set_enabled':
>> lib/powercap.c:79:40: warning: '%s' directive writing up to 254 bytes into a region of size 253 [-Wformat-overflow=]
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~
......
95 | return sysfs_set_enabled(path, mode);
| ~~~~
In function 'sysfs_set_enabled',
inlined from 'powercap_set_enabled' at lib/powercap.c:95:9:
lib/powercap.c:79:9: note: 'sprintf' output between 13 and 267 bytes into a destination of size 265
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
lib/powercap.c: In function 'powercap_zone_set_enabled':
>> lib/powercap.c:79:40: warning: '%s' directive writing up to 254 bytes into a region of size 253 [-Wformat-overflow=]
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~
......
203 | return sysfs_set_enabled(path, mode);
| ~~~~
In function 'sysfs_set_enabled',
inlined from 'powercap_zone_set_enabled' at lib/powercap.c:203:9:
lib/powercap.c:79:9: note: 'sprintf' output between 13 and 267 bytes into a destination of size 265
79 | sprintf(command, "echo -n %c > %s", yes_no, path);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-11-03 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-19 12:42 [PATCH] " Vishnu Sanal T
2024-10-21 20:36 ` Shuah Khan
2024-10-30 15:27 ` [PATCH v2] " Vishnu Sanal T
2024-10-30 16:57 ` John B. Wyatt IV
2024-11-03 16:27 ` kernel test robot [this message]
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=202411040029.mXFFVJ8w-lkp@intel.com \
--to=lkp@intel.com \
--cc=jkacur@redhat.com \
--cc=jwyatt@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=shuah@kernel.org \
--cc=t.v.s10123@gmail.com \
--cc=trenn@suse.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
Powered by JetHome