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]
Message-ID: <20180410073906.GC10141@kuha.fi.intel.com>
Date:   Tue, 10 Apr 2018 10:39:06 +0300
From:   Heikki Krogerus <heikki.krogerus@...ux.intel.com>
To:     Tobias Regnery <tobias.regnery@...il.com>
Cc:     gregkh@...uxfoundation.org, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb: typec: ucsi: fix tracepoint related build error

Hi Tobias,

On Mon, Apr 09, 2018 at 01:40:53PM +0200, Tobias Regnery wrote:
> You are right, building a defconfig, enable the UCSI driver and disable
> CONFIG_FTRACE indeed builds without problems. So it must be some other
> combination of config options. Attached is the randconfig which triggers
> the problem with linux-next from today.
> 
> Regardless of the root cause, building trace.c conditionally on
> CONFIG_TRACING works and the build failure goes away. Grepping through
> the tree this seems to be the right option to depend on, as other users
> of tracepoints are doing the same.

Fair enough. I'll send a fix for that.


Thanks,

-- 
heikki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ