linux-kernel - Re: linux-next: Tree for Jun 27 (vfio)

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:	Wed, 27 Jun 2012 13:20:37 -0600
From:	Alex Williamson <alex.williamson@...hat.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	KVM <kvm@...r.kernel.org>
Subject: Re: linux-next: Tree for Jun 27 (vfio)

On Wed, 2012-06-27 at 09:09 -0700, Randy Dunlap wrote:
> On 06/26/2012 08:22 PM, Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > This tree was not built between each merge, but only after merging all
> > the trees.
> > 
> > Changes since 20120626:
> > 
> > New tree: vfio
> 
> 
> on x86_64:
> 
>   CC [M]  drivers/vfio/vfio.o
> drivers/vfio/vfio.c: In function 'vfio_device_release':
> drivers/vfio/vfio.c:412:2: error: 'TASK_NORMAL' undeclared (first use in this function)
> drivers/vfio/vfio.c:412:2: note: each undeclared identifier is reported only once for each function it appears in
> drivers/vfio/vfio.c: In function 'vfio_del_group_dev':
> 
> drivers/vfio/vfio.c:695:2: error: 'TASK_UNINTERRUPTIBLE' undeclared (first use in this function)
> drivers/vfio/vfio.c:695:2: error: implicit declaration of function 'schedule'
> *** [drivers/vfio/vfio.o] Error 1
> 
> 
> Full randconfig file is attached.

Thanks for the report, this should be fixed in tomorrow's tree.  Thanks,

Alex

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/