From: kernel test robot <[email protected]>
To: Ammar Faizi <[email protected]>,
GNU/Weeb Mailing List <[email protected]>
Cc: [email protected]
Subject: [ammarfaizi2-block:google/android/kernel/common/android-4.9-q-release 5885/9999] fs/f2fs/data.c:417:47: sparse: sparse: Using plain integer as NULL pointer
Date: Sun, 21 Aug 2022 12:58:16 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
tree: https://github.com/ammarfaizi2/linux-block google/android/kernel/common/android-4.9-q-release
head: 8c62b2bd034cfb52860b9e3f333b1ef587052af2
commit: 39373df2d0c858d7a6544cbd37c108375c15be00 [5885/9999] Revert: "f2fs: check last page index in cached bio to decide submission"
config: i386-randconfig-s002 (https://download.01.org/0day-ci/archive/20220821/[email protected]/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/ammarfaizi2/linux-block/commit/39373df2d0c858d7a6544cbd37c108375c15be00
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block google/android/kernel/common/android-4.9-q-release
git checkout 39373df2d0c858d7a6544cbd37c108375c15be00
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/md/ fs/f2fs/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <[email protected]>
sparse warnings: (new ones prefixed by >>)
>> fs/f2fs/data.c:417:47: sparse: sparse: Using plain integer as NULL pointer
In file included from fs/f2fs/data.c:21:0:
fs/f2fs/f2fs.h: In function '__mark_inode_dirty_flag':
fs/f2fs/f2fs.h:2339:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
if (set)
^
fs/f2fs/f2fs.h:2341:2: note: here
case FI_DATA_EXIST:
^~~~
arch/x86/include/asm/bitops.h: Assembler messages:
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
arch/x86/include/asm/bitops.h:206: Warning: no instruction mnemonic suffix given and no register operands; using default for `bts'
vim +417 fs/f2fs/data.c
c4127260dcb92a Jaegeuk Kim 2017-05-10 414
9bc576a6cfda59 Jaegeuk Kim 2017-05-10 415 void f2fs_submit_merged_write(struct f2fs_sb_info *sbi, enum page_type type)
0c3a579758362d Chao Yu 2016-01-18 416 {
c4127260dcb92a Jaegeuk Kim 2017-05-10 @417 __submit_merged_write_cond(sbi, NULL, 0, 0, type, true);
0c3a579758362d Chao Yu 2016-01-18 418 }
0c3a579758362d Chao Yu 2016-01-18 419
:::::: The code at line 417 was first introduced by commit
:::::: c4127260dcb92a8ec64794db10cbdabb6d9b2b01 f2fs: split bio cache
:::::: TO: Jaegeuk Kim <[email protected]>
:::::: CC: Jaegeuk Kim <[email protected]>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-21 4:58 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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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