From: kernel test robot <rong.a.chen@intel.com>
To: kbuild-all@lists.01.org
Subject: [kdave-btrfs-devel:misc-next 140/144] fs/btrfs/scrub.c:75:44: sparse: sparse: dubious one-bit signed bitfield
Date: Fri, 20 Nov 2020 08:23:56 +0800 [thread overview]
Message-ID: <20201120002356.GU3723@shao2-debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 2842 bytes --]
tree: https://github.com/kdave/btrfs-devel.git misc-next
head: 0ece56ca6b2e45ec5c4d9e5b82fb8427cd22baa0
commit: ec9799c7e151eb438050e3ce1c41aaf5fd4d411a [140/144] btrfs: scrub: remove the anonymous structure from scrub_page
config: x86_64-randconfig-s021-20201119 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-123-g626c4742-dirty
# https://github.com/kdave/btrfs-devel/commit/ec9799c7e151eb438050e3ce1c41aaf5fd4d411a
git remote add kdave-btrfs-devel https://github.com/kdave/btrfs-devel.git
git fetch --no-tags kdave-btrfs-devel misc-next
git checkout ec9799c7e151eb438050e3ce1c41aaf5fd4d411a
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <rong.a.chen@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> fs/btrfs/scrub.c:75:44: sparse: sparse: dubious one-bit signed bitfield
fs/btrfs/scrub.c:76:43: sparse: sparse: dubious one-bit signed bitfield
vim +75 fs/btrfs/scrub.c
af8e2d1df9848b3 Miao Xie 2014-10-23 62
a2de733c78fa7af Arne Jansen 2011-03-08 63 struct scrub_page {
b5d67f64f9bc656 Stefan Behrens 2012-03-27 64 struct scrub_block *sblock;
b5d67f64f9bc656 Stefan Behrens 2012-03-27 65 struct page *page;
442a4f6308e694e Stefan Behrens 2012-05-25 66 struct btrfs_device *dev;
5a6ac9eacb49143 Miao Xie 2014-11-06 67 struct list_head list;
a2de733c78fa7af Arne Jansen 2011-03-08 68 u64 flags; /* extent flags */
a2de733c78fa7af Arne Jansen 2011-03-08 69 u64 generation;
b5d67f64f9bc656 Stefan Behrens 2012-03-27 70 u64 logical;
b5d67f64f9bc656 Stefan Behrens 2012-03-27 71 u64 physical;
ff023aac31198e8 Stefan Behrens 2012-11-06 72 u64 physical_for_dev_replace;
570193454a5841a Zhao Lei 2015-01-20 73 atomic_t refs;
ec9799c7e151eb4 Qu Wenruo 2020-11-13 74 u8 mirror_num;
ec9799c7e151eb4 Qu Wenruo 2020-11-13 @75 int have_csum:1;
ec9799c7e151eb4 Qu Wenruo 2020-11-13 76 int io_error:1;
a2de733c78fa7af Arne Jansen 2011-03-08 77 u8 csum[BTRFS_CSUM_SIZE];
af8e2d1df9848b3 Miao Xie 2014-10-23 78
af8e2d1df9848b3 Miao Xie 2014-10-23 79 struct scrub_recover *recover;
a2de733c78fa7af Arne Jansen 2011-03-08 80 };
a2de733c78fa7af Arne Jansen 2011-03-08 81
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
_______________________________________________
kbuild mailing list -- kbuild(a)lists.01.org
To unsubscribe send an email to kbuild-leave(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 32765 bytes --]
next reply other threads:[~2020-11-20 0:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 0:23 kernel test robot [this message]
2020-11-20 1:22 ` [kdave-btrfs-devel:misc-next 140/144] fs/btrfs/scrub.c:75:44: sparse: sparse: dubious one-bit signed bitfield Qu Wenruo
2020-11-23 15:51 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2020-11-19 23:59 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=20201120002356.GU3723@shao2-debian \
--to=rong.a.chen@intel.com \
--cc=kbuild-all@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.