From: kernel test robot <lkp@intel.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: fs/exfat/fatent.c:277:1: warning: the frame size of 2064 bytes is larger than 1024 bytes
Date: Sun, 10 Oct 2021 04:06:14 +0800 [thread overview]
Message-ID: <202110100407.GLS6ZVvV-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5232 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 717478d89fe22df61a4ecf73b1adb31b5f8d1bba
commit: 4eeef098b43242ed145c83fba9989d586d707589 powerpc/44x: Remove STDBINUTILS kconfig option
date: 8 months ago
config: powerpc64-randconfig-r035-20211010 (attached as .config)
compiler: powerpc-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4eeef098b43242ed145c83fba9989d586d707589
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 4eeef098b43242ed145c83fba9989d586d707589
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
fs/exfat/fatent.c: In function 'exfat_zeroed_cluster':
>> fs/exfat/fatent.c:277:1: warning: the frame size of 2064 bytes is larger than 1024 bytes [-Wframe-larger-than=]
277 | }
| ^
vim +277 fs/exfat/fatent.c
31023864e67a5f Namjae Jeon 2020-03-02 231
31023864e67a5f Namjae Jeon 2020-03-02 232 int exfat_zeroed_cluster(struct inode *dir, unsigned int clu)
31023864e67a5f Namjae Jeon 2020-03-02 233 {
31023864e67a5f Namjae Jeon 2020-03-02 234 struct super_block *sb = dir->i_sb;
31023864e67a5f Namjae Jeon 2020-03-02 235 struct exfat_sb_info *sbi = EXFAT_SB(sb);
31023864e67a5f Namjae Jeon 2020-03-02 236 struct buffer_head *bhs[MAX_BUF_PER_PAGE];
31023864e67a5f Namjae Jeon 2020-03-02 237 int nr_bhs = MAX_BUF_PER_PAGE;
31023864e67a5f Namjae Jeon 2020-03-02 238 sector_t blknr, last_blknr;
31023864e67a5f Namjae Jeon 2020-03-02 239 int err, i, n;
31023864e67a5f Namjae Jeon 2020-03-02 240
31023864e67a5f Namjae Jeon 2020-03-02 241 blknr = exfat_cluster_to_sector(sbi, clu);
31023864e67a5f Namjae Jeon 2020-03-02 242 last_blknr = blknr + sbi->sect_per_clus;
31023864e67a5f Namjae Jeon 2020-03-02 243
31023864e67a5f Namjae Jeon 2020-03-02 244 if (last_blknr > sbi->num_sectors && sbi->num_sectors > 0) {
31023864e67a5f Namjae Jeon 2020-03-02 245 exfat_fs_error_ratelimit(sb,
31023864e67a5f Namjae Jeon 2020-03-02 246 "%s: out of range(sect:%llu len:%u)",
31023864e67a5f Namjae Jeon 2020-03-02 247 __func__, (unsigned long long)blknr,
31023864e67a5f Namjae Jeon 2020-03-02 248 sbi->sect_per_clus);
31023864e67a5f Namjae Jeon 2020-03-02 249 return -EIO;
31023864e67a5f Namjae Jeon 2020-03-02 250 }
31023864e67a5f Namjae Jeon 2020-03-02 251
31023864e67a5f Namjae Jeon 2020-03-02 252 /* Zeroing the unused blocks on this cluster */
31023864e67a5f Namjae Jeon 2020-03-02 253 while (blknr < last_blknr) {
4dc7d35e09ba78 Tetsuhiro Kohada 2020-06-24 254 for (n = 0; n < nr_bhs && blknr < last_blknr; n++, blknr++) {
31023864e67a5f Namjae Jeon 2020-03-02 255 bhs[n] = sb_getblk(sb, blknr);
31023864e67a5f Namjae Jeon 2020-03-02 256 if (!bhs[n]) {
31023864e67a5f Namjae Jeon 2020-03-02 257 err = -ENOMEM;
31023864e67a5f Namjae Jeon 2020-03-02 258 goto release_bhs;
31023864e67a5f Namjae Jeon 2020-03-02 259 }
31023864e67a5f Namjae Jeon 2020-03-02 260 memset(bhs[n]->b_data, 0, sb->s_blocksize);
31023864e67a5f Namjae Jeon 2020-03-02 261 }
31023864e67a5f Namjae Jeon 2020-03-02 262
4dc7d35e09ba78 Tetsuhiro Kohada 2020-06-24 263 err = exfat_update_bhs(bhs, n, IS_DIRSYNC(dir));
31023864e67a5f Namjae Jeon 2020-03-02 264 if (err)
31023864e67a5f Namjae Jeon 2020-03-02 265 goto release_bhs;
31023864e67a5f Namjae Jeon 2020-03-02 266
31023864e67a5f Namjae Jeon 2020-03-02 267 for (i = 0; i < n; i++)
31023864e67a5f Namjae Jeon 2020-03-02 268 brelse(bhs[i]);
4dc7d35e09ba78 Tetsuhiro Kohada 2020-06-24 269 }
31023864e67a5f Namjae Jeon 2020-03-02 270 return 0;
31023864e67a5f Namjae Jeon 2020-03-02 271
31023864e67a5f Namjae Jeon 2020-03-02 272 release_bhs:
d1727d55c0327e Joe Perches 2020-04-24 273 exfat_err(sb, "failed zeroed sect %llu\n", (unsigned long long)blknr);
31023864e67a5f Namjae Jeon 2020-03-02 274 for (i = 0; i < n; i++)
31023864e67a5f Namjae Jeon 2020-03-02 275 bforget(bhs[i]);
31023864e67a5f Namjae Jeon 2020-03-02 276 return err;
31023864e67a5f Namjae Jeon 2020-03-02 @277 }
31023864e67a5f Namjae Jeon 2020-03-02 278
:::::: The code at line 277 was first introduced by commit
:::::: 31023864e67a5f390cefbe92f72343027dc3aa33 exfat: add fat entry operations
:::::: TO: Namjae Jeon <namjae.jeon@samsung.com>
:::::: CC: Al Viro <viro@zeniv.linux.org.uk>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 40140 bytes --]
reply other threads:[~2021-10-09 20:07 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=202110100407.GLS6ZVvV-lkp@intel.com \
--to=lkp@intel.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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