From: Juergen Gross <jgross@suse.com>
To: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Paul Durrant <paul.durrant@citrix.com>
Subject: Re: drivers/xen/manage.c:337:60: warning: '%s' directive output may be truncated writing up to 95 bytes into a region of size 12
Date: Mon, 4 Dec 2023 08:35:55 +0100 [thread overview]
Message-ID: <75dcf0e7-e54d-48db-a420-3c731b6f77d8@suse.com> (raw)
In-Reply-To: <202312040309.sACmAKoo-lkp@intel.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 4247 bytes --]
On 03.12.23 20:55, kernel test robot wrote:
> Hi Juergen,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 33cc938e65a98f1d29d0a18403dbbee050dcad9a
> commit: 44b3c7af02ca2701b6b90ee30c9d1d9c3ae07653 xenbus: advertise control feature flags
> date: 7 years ago
> config: x86_64-randconfig-015-20231009 (https://download.01.org/0day-ci/archive/20231204/202312040309.sACmAKoo-lkp@intel.com/config)
> 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/20231204/202312040309.sACmAKoo-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/202312040309.sACmAKoo-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/kobject.h:21,
> from include/linux/device.h:17,
> from include/linux/node.h:17,
> from include/linux/cpu.h:16,
> from include/linux/stop_machine.h:4,
> from drivers/xen/manage.c:12:
> include/linux/sysfs.h: In function 'sysfs_get_dirent':
> include/linux/sysfs.h:517:44: warning: pointer targets in passing argument 2 of 'kernfs_find_and_get' differ in signedness [-Wpointer-sign]
> 517 | return kernfs_find_and_get(parent, name);
> | ^~~~
> | |
> | const unsigned char *
> In file included from include/linux/sysfs.h:15:
> include/linux/kernfs.h:440:57: note: expected 'const char *' but argument is of type 'const unsigned char *'
> 440 | kernfs_find_and_get(struct kernfs_node *kn, const char *name)
> | ~~~~~~~~~~~~^~~~
> drivers/xen/manage.c: In function 'shutdown_event':
>>> drivers/xen/manage.c:337:60: warning: '%s' directive output may be truncated writing up to 95 bytes into a region of size 12 [-Wformat-truncation=]
> 337 | snprintf(node, FEATURE_PATH_SIZE, "feature-%s",
> | ^~
> In function 'setup_shutdown_watcher',
> inlined from 'shutdown_event' at drivers/xen/manage.c:349:2:
> drivers/xen/manage.c:337:17: note: 'snprintf' output between 9 and 104 bytes into a destination of size 20
> 337 | snprintf(node, FEATURE_PATH_SIZE, "feature-%s",
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 338 | shutdown_handlers[idx].command);
> | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IMHO this is a false analysis.
shutdown_handlers[] is:
struct shutdown_handler {
#define SHUTDOWN_CMD_SIZE 11
const char command[SHUTDOWN_CMD_SIZE];
bool flag;
void (*cb)(void);
};
static struct shutdown_handler shutdown_handlers[] = {
{ "poweroff", true, do_poweroff },
{ "halt", false, do_poweroff },
{ "reboot", true, do_reboot },
#ifdef CONFIG_HIBERNATE_CALLBACKS
{ "suspend", true, do_suspend },
#endif
};
And it is never changed.
We have:
#define FEATURE_PATH_SIZE (SHUTDOWN_CMD_SIZE + sizeof("feature-"))
char node[FEATURE_PATH_SIZE];
So how on earth could the snprintf() destination not be large enough?
> vim +337 drivers/xen/manage.c
>
> 333
> 334 for (idx = 0; idx < ARRAY_SIZE(shutdown_handlers); idx++) {
> 335 if (!shutdown_handlers[idx].flag)
> 336 continue;
> > 337 snprintf(node, FEATURE_PATH_SIZE, "feature-%s",
> 338 shutdown_handlers[idx].command);
> 339 xenbus_printf(XBT_NIL, "control", node, "%u", 1);
> 340 }
> 341
> 342 return 0;
> 343 }
> 344
>
Juergen
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-12-04 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 19:55 drivers/xen/manage.c:337:60: warning: '%s' directive output may be truncated writing up to 95 bytes into a region of size 12 kernel test robot
2023-12-04 7:35 ` Juergen Gross [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-18 20:08 kernel test robot
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=75dcf0e7-e54d-48db-a420-3c731b6f77d8@suse.com \
--to=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul.durrant@citrix.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