linux-kernel - Re: [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to hyperv.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 8 Dec 2016 16:56:56 +0100
From:   "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To:     KY Srinivasan <kys@...rosoft.com>
Cc:     kbuild test robot <lkp@...el.com>,
        "kys@...hange.microsoft.com" <kys@...hange.microsoft.com>,
        "olaf@...fle.de" <olaf@...fle.de>,
        "jasowang@...hat.com" <jasowang@...hat.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "bjorn.helgaas@...il.com" <bjorn.helgaas@...il.com>,
        "kbuild-all@...org" <kbuild-all@...org>,
        "apw@...onical.com" <apw@...onical.com>,
        "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
        "leann.ogasawara@...onical.com" <leann.ogasawara@...onical.com>
Subject: Re: [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to
 hyperv.h

On Thu, Dec 08, 2016 at 03:26:06PM +0000, KY Srinivasan wrote:
> 
> 
> > -----Original Message-----
> > From: devel [mailto:driverdev-devel-bounces@...uxdriverproject.org] On
> > Behalf Of kbuild test robot
> > Sent: Thursday, December 8, 2016 1:50 AM
> > To: kys@...hange.microsoft.com
> > Cc: olaf@...fle.de; gregkh@...uxfoundation.org; jasowang@...hat.com;
> > Haiyang Zhang <haiyangz@...rosoft.com>; linux-kernel@...r.kernel.org;
> > bjorn.helgaas@...il.com; kbuild-all@...org; apw@...onical.com;
> > devel@...uxdriverproject.org; leann.ogasawara@...onical.com
> > Subject: Re: [PATCH 1/3] hyperv: Move hv_pci_dev and related structs to
> > hyperv.h
> > 
> > Hi Haiyang,
> > 
> > [auto build test ERROR on next-20161208]
> > [also build test ERROR on v4.9-rc8]
> > [cannot apply to linus/master linux/master pci/next v4.9-rc8 v4.9-rc7 v4.9-
> > rc6]
> > [if your patch is applied to the wrong git tree, please drop us a note to help
> > improve the system]
> > 
> > url:
> > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub
> > .com%2F0day-ci%2Flinux%2Fcommits%2Fkys-exchange-microsoft-
> > com%2Fhyperv-Move-hv_pci_dev-and-related-structs-to-hyperv-
> > h%2F20161208-
> > 171643&data=02%7C01%7Ckys%40microsoft.com%7Ca000870068f645a67492
> > 08d41f4fa963%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6361678
> > 75686353145&sdata=2cR2dMEa6sjz94NYUFMx5qC8hEVvXF6uokmCCny%2FgL
> > E%3D&reserved=0
> > config: x86_64-randconfig-x012-201649 (attached as .config)
> > compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
> > reproduce:
> >         # save the attached .config to linux build tree
> >         make ARCH=x86_64
> > 
> > All errors (new ones prefixed by >>):
> > 
> >    In file included from drivers/hid/hid-hyperv.c:22:0:
> > >> include/linux/hyperv.h:1660:25: error: field 'msi_info' has incomplete type
> >      struct msi_domain_info msi_info;
> >                             ^~~~~~~~
> > 
> > vim +/msi_info +1660 include/linux/hyperv.h
> > 
> >   1654		struct semaphore enum_sem;
> >   1655		struct list_head resources_for_children;
> >   1656
> >   1657		struct list_head children;
> >   1658		struct list_head dr_list;
> >   1659
> > > 1660		struct msi_domain_info msi_info;
> >   1661		struct msi_controller msi_chip;
> >   1662		struct irq_domain *irq_domain;
> >   1663	};
> > 
> 
> 
> Greg,
> 
> I sent this patch set to show how we plan to use the API to check if a device is a 
> VMBUS device. Given that multiple trees are involved, the patches were based on
> the linux-next tree. I was planning on submitting these patches with minimal
> inter-tree dependency. 

Ok, but how does this simple patch fail so badly?  Maybe just wait for
after 4.10-rc1 is out and then try this as everything will be synced up
then?  It's pretty much past the merge window for all subsystems now
anyway...

thanks,

greg k-h