From: kbuild test robot <lkp@intel.com>
To: "zhangyi (F)" <yi.zhang@huawei.com>
Cc: kbuild-all@01.org, linux-ext4@vger.kernel.org, tytso@mit.edu,
jack@suse.cz, adilger.kernel@dilger.ca, yi.zhang@huawei.com
Subject: Re: [PATCH v2] ext4: fix potential use after free in system zone via remount with noblock_validity
Date: Thu, 8 Aug 2019 11:03:04 +0800 [thread overview]
Message-ID: <201908081107.DkPpgosg%lkp@intel.com> (raw)
In-Reply-To: <1564755566-4378-1-git-send-email-yi.zhang@huawei.com>
Hi "zhangyi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[cannot apply to v5.3-rc3 next-20190807]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/zhangyi-F/ext4-fix-potential-use-after-free-in-system-zone-via-remount-with-noblock_validity/20190804-163619
reproduce:
# apt-get install sparse
# sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
make ARCH=x86_64 allmodconfig
make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
include/linux/sched.h:609:43: sparse: sparse: bad integer constant expression
include/linux/sched.h:609:73: sparse: sparse: invalid named zero-width bitfield `value'
include/linux/sched.h:610:43: sparse: sparse: bad integer constant expression
include/linux/sched.h:610:67: sparse: sparse: invalid named zero-width bitfield `bucket_id'
include/linux/rbtree.h:84:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
include/linux/rbtree.h:84:9: sparse: struct rb_node [noderef] <asn:4> *
include/linux/rbtree.h:84:9: sparse: struct rb_node *
>> fs/ext4/block_validity.c:252:9: sparse: sparse: incompatible types in comparison expression (different address spaces):
>> fs/ext4/block_validity.c:252:9: sparse: struct rb_node [noderef] <asn:4> *
>> fs/ext4/block_validity.c:252:9: sparse: struct rb_node *
vim +252 fs/ext4/block_validity.c
246
247 /* Called when the filesystem is unmounted */
248 void ext4_release_system_zone(struct super_block *sb)
249 {
250 struct ext4_system_zone *entry, *n;
251
> 252 rcu_assign_pointer(EXT4_SB(sb)->system_blks.rb_node, NULL);
253
254 rbtree_postorder_for_each_entry_safe(entry, n,
255 &EXT4_SB(sb)->system_blks, node)
256 call_rcu(&entry->rcu, destroy_system_zone);
257 }
258
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
prev parent reply other threads:[~2019-08-08 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 14:19 [PATCH v2] ext4: fix potential use after free in system zone via remount with noblock_validity zhangyi (F)
2019-08-08 3:03 ` kbuild test robot [this message]
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=201908081107.DkPpgosg%lkp@intel.com \
--to=lkp@intel.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=kbuild-all@01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.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).