public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Isaac J. Manjarres" <isaacmanjarres@google.com>,
	tglx@linutronix.de, "Rafael J. Wysocki" <rafael@kernel.org>,
	Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Cc: oe-kbuild-all@lists.linux.dev, saravanak@google.com,
	Manish Varma <varmam@google.com>,
	Kelly Rossmoyer <krossmo@google.com>,
	"Isaac J . Manjarres" <isaacmanjarres@google.com>,
	kernel-team@android.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v4] fs: Improve eventpoll logging to stop indicting timerfd
Date: Wed, 5 Jun 2024 06:13:11 +0800	[thread overview]
Message-ID: <202406050504.UvdlPAQ0-lkp@intel.com> (raw)
In-Reply-To: <20240604173606.998721-1-isaacmanjarres@google.com>

Hi Isaac,

kernel test robot noticed the following build warnings:

[auto build test WARNING on rafael-pm/linux-next]
[also build test WARNING on rafael-pm/bleeding-edge linus/master v6.10-rc2 next-20240604]
[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/Isaac-J-Manjarres/fs-Improve-eventpoll-logging-to-stop-indicting-timerfd/20240605-013918
base:   https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link:    https://lore.kernel.org/r/20240604173606.998721-1-isaacmanjarres%40google.com
patch subject: [PATCH v4] fs: Improve eventpoll logging to stop indicting timerfd
config: um-i386_defconfig (https://download.01.org/0day-ci/archive/20240605/202406050504.UvdlPAQ0-lkp@intel.com/config)
compiler: gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240605/202406050504.UvdlPAQ0-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/202406050504.UvdlPAQ0-lkp@intel.com/

All warnings (new ones prefixed by >>):

   drivers/base/power/wakeup.c: In function 'wakeup_source_register':
>> drivers/base/power/wakeup.c:223:9: warning: function 'wakeup_source_register' might be a candidate for 'gnu_printf' format attribute [-Wsuggest-attribute=format]
     223 |         vsnprintf(name, sizeof(name), fmt, args);
         |         ^~~~~~~~~


vim +223 drivers/base/power/wakeup.c

   208	
   209	/**
   210	 * wakeup_source_register - Create wakeup source and add it to the list.
   211	 * @dev: Device this wakeup source is associated with (or NULL if virtual).
   212	 * @fmt: format string for the wakeup source name
   213	 */
   214	struct wakeup_source *wakeup_source_register(struct device *dev,
   215						     const char *fmt, ...)
   216	{
   217		struct wakeup_source *ws;
   218		int ret;
   219		char name[128];
   220		va_list args;
   221	
   222		va_start(args, fmt);
 > 223		vsnprintf(name, sizeof(name), fmt, args);
   224		va_end(args);
   225	
   226		ws = wakeup_source_create(name);
   227		if (ws) {
   228			if (!dev || device_is_registered(dev)) {
   229				ret = wakeup_source_sysfs_add(dev, ws);
   230				if (ret) {
   231					wakeup_source_free(ws);
   232					return NULL;
   233				}
   234			}
   235			wakeup_source_add(ws);
   236		}
   237		return ws;
   238	}
   239	EXPORT_SYMBOL_GPL(wakeup_source_register);
   240	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

      reply	other threads:[~2024-06-04 22:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 17:36 [PATCH v4] fs: Improve eventpoll logging to stop indicting timerfd Isaac J. Manjarres
2024-06-04 22:13 ` 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=202406050504.UvdlPAQ0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brauner@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=isaacmanjarres@google.com \
    --cc=jack@suse.cz \
    --cc=kernel-team@android.com \
    --cc=krossmo@google.com \
    --cc=len.brown@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=saravanak@google.com \
    --cc=tglx@linutronix.de \
    --cc=varmam@google.com \
    --cc=viro@zeniv.linux.org.uk \
    /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