From: kernel test robot <lkp@intel.com>
To: Biancaa Ramesh <biancaa2210329@ssn.edu.in>, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Biancaa Ramesh <biancaa2210329@ssn.edu.in>
Subject: Re: [PATCH] dma-buf: improve dma_buf_show_fdinfo output
Date: Wed, 22 Oct 2025 09:47:29 +0800 [thread overview]
Message-ID: <202510220948.fae9xJYg-lkp@intel.com> (raw)
In-Reply-To: <20251021133132.29751-1-biancaa2210329@ssn.edu.in>
Hi Biancaa,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.18-rc2 next-20251021]
[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/Biancaa-Ramesh/dma-buf-improve-dma_buf_show_fdinfo-output/20251021-213541
base: linus/master
patch link: https://lore.kernel.org/r/20251021133132.29751-1-biancaa2210329%40ssn.edu.in
patch subject: [PATCH] dma-buf: improve dma_buf_show_fdinfo output
config: x86_64-randconfig-002-20251022 (https://download.01.org/0day-ci/archive/20251022/202510220948.fae9xJYg-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251022/202510220948.fae9xJYg-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/202510220948.fae9xJYg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/dma-buf/dma-buf.c:581:36: warning: format specifies type 'unsigned long' but the argument has type 'unsigned int' [-Wformat]
581 | seq_printf(s, "flags:\t%lu\n", f->f_flags);
| ~~~ ^~~~~~~~~~
| %u
>> drivers/dma-buf/dma-buf.c:582:36: warning: format specifies type 'unsigned long long' but the argument has type 'size_t' (aka 'unsigned long') [-Wformat]
582 | seq_printf(s, "size:\t%llu\n", dmabuf->size);
| ~~~~ ^~~~~~~~~~~~
| %zu
drivers/dma-buf/dma-buf.c:584:62: error: no member named 'num_attachments' in 'struct dma_buf'; did you mean 'attachments'?
584 | seq_printf(s, "attachments:\t%d\n", atomic_read(&dmabuf->num_attachments));
| ^~~~~~~~~~~~~~~
| attachments
include/linux/dma-buf.h:315:19: note: 'attachments' declared here
315 | struct list_head attachments;
| ^
drivers/dma-buf/dma-buf.c:585:59: error: no member named 'num_mappings' in 'struct dma_buf'
585 | seq_printf(s, "mappings:\t%d\n", atomic_read(&dmabuf->num_mappings));
| ~~~~~~ ^
2 warnings and 2 errors generated.
vim +581 drivers/dma-buf/dma-buf.c
573
574 static void dma_buf_show_fdinfo(struct seq_file *s, struct file *f)
575 {
576 struct dma_buf *dmabuf = f->private_data;
577
578 if (!dmabuf)
579 return;
580
> 581 seq_printf(s, "flags:\t%lu\n", f->f_flags);
> 582 seq_printf(s, "size:\t%llu\n", dmabuf->size);
583 seq_printf(s, "count:\t%ld\n", file_count(dmabuf->file) - 1);
584 seq_printf(s, "attachments:\t%d\n", atomic_read(&dmabuf->num_attachments));
585 seq_printf(s, "mappings:\t%d\n", atomic_read(&dmabuf->num_mappings));
586 seq_printf(s, "exp_name:\t%s\n", dmabuf->exp_name ? dmabuf->exp_name : "N/A");
587
588 spin_lock(&dmabuf->name_lock);
589 if (dmabuf->name)
590 seq_printf(s, "name:\t%s\n", dmabuf->name);
591 spin_unlock(&dmabuf->name_lock);
592 }
593
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-22 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 13:31 [PATCH] dma-buf: improve dma_buf_show_fdinfo output Biancaa Ramesh
2025-10-22 0:41 ` kernel test robot
2025-10-22 1:47 ` kernel test robot [this message]
2025-10-22 2:40 ` 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=202510220948.fae9xJYg-lkp@intel.com \
--to=lkp@intel.com \
--cc=biancaa2210329@ssn.edu.in \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox