From: kernel test robot <lkp@intel.com>
To: "Yuezhang.Mo@sony.com" <Yuezhang.Mo@sony.com>,
"linkinjeon@kernel.org" <linkinjeon@kernel.org>,
"sj1557.seo@samsung.com" <sj1557.seo@samsung.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Andy.Wu@sony.com" <Andy.Wu@sony.com>,
"Wataru.Aoyama@sony.com" <Wataru.Aoyama@sony.com>,
"cpgs@samsung.com" <cpgs@samsung.com>
Subject: Re: [PATCH v5 1/2] exfat: change to get file size from DataLength
Date: Fri, 1 Dec 2023 01:10:10 +0800 [thread overview]
Message-ID: <202312010044.6CIJOsWq-lkp@intel.com> (raw)
In-Reply-To: <PUZPR04MB6316F0640983B00CC55D903F8182A@PUZPR04MB6316.apcprd04.prod.outlook.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on v6.7-rc3 next-20231130]
[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/Yuezhang-Mo-sony-com/exfat-do-not-zero-the-extended-part/20231130-164222
base: linus/master
patch link: https://lore.kernel.org/r/PUZPR04MB6316F0640983B00CC55D903F8182A%40PUZPR04MB6316.apcprd04.prod.outlook.com
patch subject: [PATCH v5 1/2] exfat: change to get file size from DataLength
config: i386-allmodconfig (https://download.01.org/0day-ci/archive/20231201/202312010044.6CIJOsWq-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231201/202312010044.6CIJOsWq-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/202312010044.6CIJOsWq-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/exfat/file.c:543:22: warning: format specifies type 'long' but the argument has type 'ssize_t' (aka 'int') [-Wformat]
valid_size, pos, ret);
^~~
fs/exfat/exfat_fs.h:545:51: note: expanded from macro 'exfat_err'
pr_err("exFAT-fs (%s): " fmt "\n", (sb)->s_id, ##__VA_ARGS__)
~~~ ^~~~~~~~~~~
include/linux/printk.h:498:33: note: expanded from macro 'pr_err'
printk(KERN_ERR pr_fmt(fmt), ##__VA_ARGS__)
~~~ ^~~~~~~~~~~
include/linux/printk.h:455:60: note: expanded from macro 'printk'
#define printk(fmt, ...) printk_index_wrap(_printk, fmt, ##__VA_ARGS__)
~~~ ^~~~~~~~~~~
include/linux/printk.h:427:19: note: expanded from macro 'printk_index_wrap'
_p_func(_fmt, ##__VA_ARGS__); \
~~~~ ^~~~~~~~~~~
1 warning generated.
vim +543 fs/exfat/file.c
520
521 static ssize_t exfat_file_write_iter(struct kiocb *iocb, struct iov_iter *iter)
522 {
523 ssize_t ret;
524 struct file *file = iocb->ki_filp;
525 struct inode *inode = file_inode(file);
526 struct exfat_inode_info *ei = EXFAT_I(inode);
527 loff_t pos = iocb->ki_pos;
528 loff_t valid_size;
529
530 inode_lock(inode);
531
532 valid_size = ei->valid_size;
533
534 ret = generic_write_checks(iocb, iter);
535 if (ret < 0)
536 goto unlock;
537
538 if (pos > valid_size) {
539 ret = exfat_file_zeroed_range(file, valid_size, pos);
540 if (ret < 0 && ret != -ENOSPC) {
541 exfat_err(inode->i_sb,
542 "write: fail to zero from %llu to %llu(%ld)",
> 543 valid_size, pos, ret);
544 }
545 if (ret < 0)
546 goto unlock;
547 }
548
549 ret = __generic_file_write_iter(iocb, iter);
550 if (ret < 0)
551 goto unlock;
552
553 inode_unlock(inode);
554
555 if (pos > valid_size)
556 pos = valid_size;
557
558 if (iocb_is_dsync(iocb) && iocb->ki_pos > pos) {
559 ssize_t err = vfs_fsync_range(file, pos, iocb->ki_pos - 1,
560 iocb->ki_flags & IOCB_SYNC);
561 if (err < 0)
562 return err;
563 }
564
565 return ret;
566
567 unlock:
568 inode_unlock(inode);
569
570 return ret;
571 }
572
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-11-30 17:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 9:58 [PATCH v4 0/2] exfat: get file size from DataLength Yuezhang.Mo
2023-11-30 3:09 ` [PATCH v5 " Yuezhang.Mo
2023-12-05 10:16 ` [PATCH v6 " Yuezhang.Mo
2023-12-12 4:12 ` Namjae Jeon
[not found] ` <PUZPR04MB63160A6FD8E7EF04E4342B1B818EA@PUZPR04MB6316.apcprd04.prod.outlook.com>
2023-12-12 10:29 ` Yuezhang.Mo
2023-12-13 4:14 ` Namjae Jeon
2023-12-05 10:16 ` [PATCH v6 1/2] exfat: change to " Yuezhang.Mo
2023-12-05 10:16 ` [PATCH v6 2/2] exfat: do not zero the extended part Yuezhang.Mo
2023-11-30 3:09 ` [PATCH v5 1/2] exfat: change to get file size from DataLength Yuezhang.Mo
2023-11-30 17:10 ` kernel test robot [this message]
2023-11-30 18:04 ` kernel test robot
2023-12-01 8:29 ` Dan Carpenter
2023-12-05 2:11 ` Sungjong Seo
2023-12-05 3:30 ` Namjae Jeon
[not found] ` <PUZPR04MB6316B8BAC361A5B2A70FD5098185A@PUZPR04MB6316.apcprd04.prod.outlook.com>
2023-12-05 5:29 ` Yuezhang.Mo
2023-11-30 3:09 ` [PATCH v5 2/2] exfat: do not zero the extended part Yuezhang.Mo
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=202312010044.6CIJOsWq-lkp@intel.com \
--to=lkp@intel.com \
--cc=Andy.Wu@sony.com \
--cc=Wataru.Aoyama@sony.com \
--cc=Yuezhang.Mo@sony.com \
--cc=cpgs@samsung.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sj1557.seo@samsung.com \
/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;
as well as URLs for NNTP newsgroup(s).