From: kernel test robot <lkp@intel.com>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] net: skb: on zero-copy formatted output to skb
Date: Sun, 3 May 2026 04:13:21 +0800 [thread overview]
Message-ID: <202605030443.Enw1fif1-lkp@intel.com> (raw)
In-Reply-To: <20260423073638.778334-1-dmantipov@yandex.ru>
Hi Dmitry,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
[also build test WARNING on net/main linus/master v7.1-rc1 next-20260430]
[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/Dmitry-Antipov/net-skb-on-zero-copy-formatted-output-to-skb/20260425-175341
base: net-next/main
patch link: https://lore.kernel.org/r/20260423073638.778334-1-dmantipov%40yandex.ru
patch subject: [RFC PATCH] net: skb: on zero-copy formatted output to skb
config: sparc64-allmodconfig (https://download.01.org/0day-ci/archive/20260503/202605030443.Enw1fif1-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 5bac06718f502014fade905512f1d26d578a18f3)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260503/202605030443.Enw1fif1-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/202605030443.Enw1fif1-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> net/core/skbuff.c:7001:56: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of 'skb_printf' [-Wmissing-format-attribute]
7001 | len = vsnprintf(skb_tail_pointer(skb), size, fmt, args);
| ^
include/linux/skbuff.h:4295:5: note: 'skb_printf' declared here
4295 | int skb_printf(struct sk_buff *skb, const char *fmt, ...);
| ^
1 warning generated.
vim +7001 net/core/skbuff.c
6994
6995 int skb_printf(struct sk_buff *skb, const char *fmt, ...)
6996 {
6997 int len, size = skb_availroom(skb);
6998 va_list args;
6999
7000 va_start(args, fmt);
> 7001 len = vsnprintf(skb_tail_pointer(skb), size, fmt, args);
7002 va_end(args);
7003
7004 if (unlikely(len >= size))
7005 return -ENOSPC;
7006
7007 skb->tail += len;
7008 skb->len += len;
7009 return len;
7010 }
7011 EXPORT_SYMBOL(skb_printf);
7012
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-05-02 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 7:36 [RFC PATCH] net: skb: on zero-copy formatted output to skb Dmitry Antipov
2026-04-23 9:47 ` [RFC] " bluez.test.bot
2026-04-23 12:24 ` [RFC PATCH] " Andrew Lunn
2026-04-23 12:40 ` Andrew Lunn
2026-04-23 16:03 ` Dmitry Antipov
2026-04-23 16:46 ` Andrew Lunn
2026-05-02 20: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=202605030443.Enw1fif1-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmantipov@yandex.ru \
--cc=llvm@lists.linux.dev \
--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 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.