From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:netfs-writeback 16/16] fs/netfs/main.c:70:6: warning: format specifies type 'int' but the argument has type 'long'
Date: Tue, 25 Jun 2024 00:29:46 +0800 [thread overview]
Message-ID: <202406250022.6NZKarFI-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git netfs-writeback
head: 4058083df1dc58322ad2ec98bcd218a43c8befac
commit: 4058083df1dc58322ad2ec98bcd218a43c8befac [16/16] netfs: Speed up buffered reading
config: i386-randconfig-006-20240624 (https://download.01.org/0day-ci/archive/20240625/202406250022.6NZKarFI-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240625/202406250022.6NZKarFI-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/202406250022.6NZKarFI-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/netfs/main.c:70:6: warning: format specifies type 'int' but the argument has type 'long' [-Wformat]
65 | "%08x %s %3d %2lx %4d @%04llx %llx/%llx",
| ~~~
| %4ld
66 | rreq->debug_id,
67 | netfs_origins[rreq->origin],
68 | refcount_read(&rreq->ref),
69 | rreq->flags,
70 | rreq->error,
| ^~~~~~~~~~~
1 warning generated.
vim +70 fs/netfs/main.c
87b57a048964ab David Howells 2022-03-04 47
87b57a048964ab David Howells 2022-03-04 48 /*
87b57a048964ab David Howells 2022-03-04 49 * Generate a list of I/O requests in /proc/fs/netfs/requests
87b57a048964ab David Howells 2022-03-04 50 */
87b57a048964ab David Howells 2022-03-04 51 static int netfs_requests_seq_show(struct seq_file *m, void *v)
87b57a048964ab David Howells 2022-03-04 52 {
87b57a048964ab David Howells 2022-03-04 53 struct netfs_io_request *rreq;
87b57a048964ab David Howells 2022-03-04 54
87b57a048964ab David Howells 2022-03-04 55 if (v == &netfs_io_requests) {
87b57a048964ab David Howells 2022-03-04 56 seq_puts(m,
4058083df1dc58 David Howells 2024-06-19 57 "REQUEST OR REF FL ERR COVERAGE\n"
4058083df1dc58 David Howells 2024-06-19 58 "======== == === == ==== =========\n"
87b57a048964ab David Howells 2022-03-04 59 );
87b57a048964ab David Howells 2022-03-04 60 return 0;
87b57a048964ab David Howells 2022-03-04 61 }
87b57a048964ab David Howells 2022-03-04 62
87b57a048964ab David Howells 2022-03-04 63 rreq = list_entry(v, struct netfs_io_request, proc_link);
87b57a048964ab David Howells 2022-03-04 64 seq_printf(m,
4058083df1dc58 David Howells 2024-06-19 65 "%08x %s %3d %2lx %4d @%04llx %llx/%llx",
87b57a048964ab David Howells 2022-03-04 66 rreq->debug_id,
87b57a048964ab David Howells 2022-03-04 67 netfs_origins[rreq->origin],
87b57a048964ab David Howells 2022-03-04 68 refcount_read(&rreq->ref),
87b57a048964ab David Howells 2022-03-04 69 rreq->flags,
87b57a048964ab David Howells 2022-03-04 @70 rreq->error,
87b57a048964ab David Howells 2022-03-04 71 rreq->start, rreq->submitted, rreq->len);
87b57a048964ab David Howells 2022-03-04 72 seq_putc(m, '\n');
87b57a048964ab David Howells 2022-03-04 73 return 0;
87b57a048964ab David Howells 2022-03-04 74 }
87b57a048964ab David Howells 2022-03-04 75
:::::: The code at line 70 was first introduced by commit
:::::: 87b57a048964abfd5f3d8b79bc55687327f5a380 netfs: Add a procfile to list in-progress requests
:::::: TO: David Howells <dhowells@redhat.com>
:::::: CC: David Howells <dhowells@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-24 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202406250022.6NZKarFI-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--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