linux-kernel - Re: linux-next: build failure after merge of the bluetooth tree

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] [day] [month] [year] [list]

Date:	Tue, 21 Feb 2012 20:29:51 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	sfr@...b.auug.org.au
Cc:	padovan@...fusion.mobi, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org, hjl.tools@...il.com,
	marcel@...tmann.org, hpa@...or.com
Subject: Re: linux-next: build failure after merge of the bluetooth tree

From: Stephen Rothwell <sfr@...b.auug.org.au>
Date: Wed, 22 Feb 2012 12:21:09 +1100

> Hi Gustavo,
> 
> After merging the bluetooth tree, today's linux-next build
> (x86_64_allmodconfig) failed like this:
> 
> net/bluetooth/hci_sock.c: In function 'hci_sock_cmsg':
> net/bluetooth/hci_sock.c:738:8: error: 'COMPAT_USE_64BIT_TIME' undeclared (first use in this function)
> 
> Caused by commit aebb77ca6ad1 ("compat: Use COMPAT_USE_64BIT_TIME in the
> Bluetooth subsystem").  That symbol doesn't exist anywhere in linux-next ...
> 
> I have used the bluetooth from next-20120221 for today.
> 
> P.S. that commit is supposedly authored by H. J. Lu but does not contain
> a Signed-off-by from him.

That patch series was meant to go in as a group, because all of the
subsequent patches depend upon patches earlier in the series.

There is zero reason you should have applied that patch into your
bluetooth subsystem tree.  The fact that it wasn't adequately build
tested either I find quite troubling.

Lots of red cards for the bluetooth maintainers today.
--
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/