From: kbuild test robot <lkp@intel.com>
To: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Cc: kbuild-all@01.org, kvm@vger.kernel.org, borntraeger@de.ibm.com,
pbonzini@redhat.com, linux-kernel@vger.kernel.org,
david@redhat.com
Subject: Re: [PATCH v4 1/1] KVM: trigger uevents when creating or destroying a VM
Date: Wed, 12 Jul 2017 09:03:24 +0800 [thread overview]
Message-ID: <201707120807.s3SrSAAa%fengguang.wu@intel.com> (raw)
In-Reply-To: <1499775163-26797-2-git-send-email-imbrenda@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 3681 bytes --]
Hi Claudio,
[auto build test ERROR on kvm/linux-next]
[also build test ERROR on v4.12 next-20170711]
[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/Claudio-Imbrenda/KVM-trigger-uevents-when-creating-or-destroying-a-VM/20170712-023748
base: https://git.kernel.org/pub/scm/virt/kvm/kvm.git linux-next
config: powerpc-defconfig (attached as .config)
compiler: powerpc64-linux-gnu-gcc (Debian 6.3.0-18) 6.3.0 20170516
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=powerpc
All errors (new ones prefixed by >>):
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function 'kvm_uevent_notify_change':
>> arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:3892:24: error: 'struct mm_struct' has no member named 'owner'
if (kvm->mm && kvm->mm->owner) {
^~
arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:3893:40: error: 'struct mm_struct' has no member named 'owner'
add_uevent_var(env, "PID=%d", kvm->mm->owner->pid);
^~
vim +3892 arch/powerpc/kvm/../../../virt/kvm/kvm_main.c
3864
3865 static void kvm_uevent_notify_change(unsigned int type, struct kvm *kvm)
3866 {
3867 struct kobj_uevent_env *env;
3868 char *tmp, *pathbuf = NULL;
3869 unsigned long long created, active;
3870
3871 if (!kvm_dev.this_device || !kvm)
3872 return;
3873
3874 spin_lock(&kvm_lock);
3875 if (type == KVM_EVENT_CREATE_VM) {
3876 kvm_createvm_count++;
3877 kvm_active_vms++;
3878 } else if (type == KVM_EVENT_DESTROY_VM) {
3879 kvm_active_vms--;
3880 }
3881 created = kvm_createvm_count;
3882 active = kvm_active_vms;
3883 spin_unlock(&kvm_lock);
3884
3885 env = kzalloc(sizeof(*env), GFP_KERNEL);
3886 if (!env)
3887 return;
3888
3889 add_uevent_var(env, "CREATED=%llu", created);
3890 add_uevent_var(env, "COUNT=%llu", active);
3891
> 3892 if (kvm->mm && kvm->mm->owner) {
3893 add_uevent_var(env, "PID=%d", kvm->mm->owner->pid);
3894 } else if (kvm->debugfs_dentry) {
3895 char p[ITOA_MAX_LEN];
3896
3897 snprintf(p, sizeof(p), "%s", kvm->debugfs_dentry->d_name.name);
3898 tmp = strchrnul(p + 1, '-');
3899 *tmp = '\0';
3900 add_uevent_var(env, "PID=%s", p);
3901 }
3902
3903 if (type == KVM_EVENT_CREATE_VM)
3904 add_uevent_var(env, "EVENT=create");
3905 else if (type == KVM_EVENT_DESTROY_VM)
3906 add_uevent_var(env, "EVENT=destroy");
3907
3908 if (kvm->debugfs_dentry) {
3909 pathbuf = kmalloc(PATH_MAX, GFP_KERNEL);
3910 if (pathbuf) {
3911 /* sizeof counts the final '\0' */
3912 int len = sizeof("STATS_PATH=") - 1;
3913 const char *pvar = "STATS_PATH=";
3914
3915 tmp = dentry_path_raw(kvm->debugfs_dentry,
3916 pathbuf + len,
3917 PATH_MAX - len);
3918 if (!IS_ERR(tmp)) {
3919 memcpy(tmp - len, pvar, len);
3920 env->envp[env->envp_idx++] = tmp - len;
3921 }
3922 }
3923 }
3924 /* no need for checks, since we are adding at most only 5 keys */
3925 env->envp[env->envp_idx++] = NULL;
3926 kobject_uevent_env(&kvm_dev.this_device->kobj, KOBJ_CHANGE, env->envp);
3927 kfree(env);
3928 kfree(pathbuf);
3929 }
3930
---
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: 23467 bytes --]
prev parent reply other threads:[~2017-07-12 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 12:12 [PATCH v4 0/1] " Claudio Imbrenda
2017-07-11 12:12 ` [PATCH v4 1/1] " Claudio Imbrenda
2017-07-11 21:13 ` kbuild test robot
2017-07-12 1: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=201707120807.s3SrSAAa%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.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
all inboxes | Powered by JetHome®