From: kbuild test robot <lkp@intel.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: kbuild-all@01.org, anand.jain@oracle.com,
linux-btrfs@vger.kernel.org, Nikolay Borisov <nborisov@suse.com>
Subject: Re: [PATCH] Revert "btrfs: fix a possible umount deadlock"
Date: Fri, 29 Jun 2018 05:53:16 +0800 [thread overview]
Message-ID: <201806290551.3XVQNhU9%fengguang.wu@intel.com> (raw)
In-Reply-To: <1530175695-301-1-git-send-email-nborisov@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2461 bytes --]
Hi Nikolay,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on v4.18-rc2]
[also build test ERROR on next-20180628]
[cannot apply to btrfs/next]
[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/Nikolay-Borisov/Revert-btrfs-fix-a-possible-umount-deadlock/20180629-044154
config: i386-randconfig-a0-201825 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
fs//btrfs/volumes.c: In function 'btrfs_close_one_device':
>> fs//btrfs/volumes.c:1041:25: error: 'free_device' undeclared (first use in this function)
call_rcu(&device->rcu, free_device);
^
fs//btrfs/volumes.c:1041:25: note: each undeclared identifier is reported only once for each function it appears in
vim +/free_device +1041 fs//btrfs/volumes.c
1006
1007 static void btrfs_close_one_device(struct btrfs_device *device)
1008 {
1009 struct btrfs_fs_devices *fs_devices = device->fs_devices;
1010 struct btrfs_device *new_device;
1011 struct rcu_string *name;
1012
1013 if (device->bdev)
1014 fs_devices->open_devices--;
1015
1016 if (test_bit(BTRFS_DEV_STATE_WRITEABLE, &device->dev_state) &&
1017 device->devid != BTRFS_DEV_REPLACE_DEVID) {
1018 list_del_init(&device->dev_alloc_list);
1019 fs_devices->rw_devices--;
1020 }
1021
1022 if (test_bit(BTRFS_DEV_STATE_MISSING, &device->dev_state))
1023 fs_devices->missing_devices--;
1024
1025 btrfs_close_bdev(device);
1026
1027 new_device = btrfs_alloc_device(NULL, &device->devid,
1028 device->uuid);
1029 BUG_ON(IS_ERR(new_device)); /* -ENOMEM */
1030
1031 /* Safe because we are under uuid_mutex */
1032 if (device->name) {
1033 name = rcu_string_strdup(device->name->str, GFP_NOFS);
1034 BUG_ON(!name); /* -ENOMEM */
1035 rcu_assign_pointer(new_device->name, name);
1036 }
1037
1038 list_replace_rcu(&device->dev_list, &new_device->dev_list);
1039 new_device->fs_devices = device->fs_devices;
1040
> 1041 call_rcu(&device->rcu, free_device);
1042 }
1043
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27668 bytes --]
next prev parent reply other threads:[~2018-06-28 21:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 8:48 [PATCH] Revert "btrfs: fix a possible umount deadlock" Nikolay Borisov
2018-06-28 21:53 ` kbuild test robot [this message]
2018-06-28 22:49 ` kbuild 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=201806290551.3XVQNhU9%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=anand.jain@oracle.com \
--cc=kbuild-all@01.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.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