mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: kernel test robot <lkp@intel.com>,
	axboe@kernel.dk, rostedt@goodmis.org, mhiramat@kernel.org,
	mathieu.desnoyers@efficios.com, akpm@linux-foundation.org,
	oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	Jason Xing <kernelxing@tencent.com>,
	Yushan Zhou <katrinzhou@tencent.com>
Subject: Re: [PATCH v4 4/5] blktrace: use rbuf->stats.full as a drop indicator in relayfs
Date: Wed, 11 Jun 2025 17:08:45 +0900	[thread overview]
Message-ID: <20250611170845.8f88347e3cba51cf15a01b21@kernel.org> (raw)
In-Reply-To: <CAL+tcoARvQVgd68HGoXXiK=+RSH12WQ_rc47B4rgtt2Eb05c0w@mail.gmail.com>

On Wed, 11 Jun 2025 13:15:40 +0800
Jason Xing <kerneljasonxing@gmail.com> wrote:

> On Wed, Jun 11, 2025 at 9:42 AM kernel test robot <lkp@intel.com> wrote:
> >
> > Hi Jason,
> >
> > kernel test robot noticed the following build warnings:
> >
> > [auto build test WARNING on axboe-block/for-next]
> > [also build test WARNING on drm-i915/for-linux-next drm-i915/for-linux-next-fixes akpm-mm/mm-everything linus/master v6.16-rc1 next-20250610]
> > [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/Jason-Xing/relayfs-abolish-prev_padding/20250610-085150
> > base:   https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
> > patch link:    https://lore.kernel.org/r/20250610004844.66688-5-kerneljasonxing%40gmail.com
> > patch subject: [PATCH v4 4/5] blktrace: use rbuf->stats.full as a drop indicator in relayfs
> > config: arc-randconfig-001-20250610
> > compiler: arc-linux-gcc (GCC) 12.4.0
> > reproduce (this is a W=1 build):
> >
> > 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/202506102340.uo7QDaVk-lkp@intel.com/
> >
> > All warnings (new ones prefixed by >>):
> >
> >    kernel/trace/blktrace.c: In function 'blk_dropped_read':
> > >> kernel/trace/blktrace.c:421:39: warning: format '%lu' expects argument of type 'long unsigned int', but argument 4 has type 'size_t' {aka 'unsigned int'} [-Wformat=]
> >      421 |         snprintf(buf, sizeof(buf), "%lu\n", dropped);
> >          |                                     ~~^     ~~~~~~~
> >          |                                       |     |
> >          |                                       |     size_t {aka unsigned int}
> >          |                                       long unsigned int
> >          |                                     %u
> 
> Well, I suppose I will fix it in the re-spin after receiving more
> comments so that I don't need to quickly respond to this minor issue.

Please update the patch and send series with my reviewed-by on 1/5.
BTW, size_t should use %zu.
Please check Documentation/core-api/printk-formats.rst

Thank you,

> 
> Thanks,
> Jason
> 
> >
> >
> > vim +421 kernel/trace/blktrace.c
> >
> >    413
> >    414  static ssize_t blk_dropped_read(struct file *filp, char __user *buffer,
> >    415                                  size_t count, loff_t *ppos)
> >    416  {
> >    417          struct blk_trace *bt = filp->private_data;
> >    418          size_t dropped = relay_stats(bt->rchan, RELAY_STATS_BUF_FULL);
> >    419          char buf[16];
> >    420
> >  > 421          snprintf(buf, sizeof(buf), "%lu\n", dropped);
> >    422
> >    423          return simple_read_from_buffer(buffer, count, ppos, buf, strlen(buf));
> >    424  }
> >    425
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2025-06-11  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-10  0:48 [PATCH v4 0/5] relayfs: misc changes Jason Xing
2025-06-10  0:48 ` [PATCH v4 1/5] relayfs: abolish prev_padding Jason Xing
2025-06-11  8:03   ` Masami Hiramatsu
2025-06-10  0:48 ` [PATCH v4 2/5] relayfs: support a counter tracking if per-cpu buffers is full Jason Xing
2025-06-10  0:48 ` [PATCH v4 3/5] relayfs: introduce getting relayfs statistics function Jason Xing
2025-06-10  0:48 ` [PATCH v4 4/5] blktrace: use rbuf->stats.full as a drop indicator in relayfs Jason Xing
2025-06-10 15:47   ` kernel test robot
2025-06-11  5:15     ` Jason Xing
2025-06-11  8:08       ` Masami Hiramatsu [this message]
2025-06-11 12:20         ` Jason Xing
2025-06-10  0:48 ` [PATCH v4 5/5] relayfs: support a counter tracking if data is too big to write Jason Xing

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=20250611170845.8f88347e3cba51cf15a01b21@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=katrinzhou@tencent.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kernelxing@tencent.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    /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

all inboxes | Powered by JetHome®