linux-kernel - Re: [PATCH] usb: musb: cppi: add missing include to fix compilation

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:	Mon, 14 May 2012 21:26:02 +0400
From:	Sergei Shtylyov <sshtylyov@...sta.com>
To:	Reinhard Tartler <Reinhard.Tartler@...ormatik.uni-erlangen.de>
CC:	Greg KH <gregkh@...uxfoundation.org>,
	Reinhard Tartler <tartler@...fau.de>,
	Felipe Balbi <balbi@...com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, vamos-dev@...ts.cs.fau.de
Subject: Re: [PATCH] usb: musb: cppi: add missing include to fix compilation

Hello.

On 05/14/2012 08:53 PM, Reinhard Tartler wrote:

>> On Mon, May 14, 2012 at 06:05:20PM +0200, Reinhard Tartler wrote:
>>> This fixes compilation as module.

>>> Signed-off-by: Reinhard Tartler<tartler@...fau.de>
>>> ---
>>>   drivers/usb/musb/cppi_dma.c |    1 +
>>>   1 file changed, 1 insertion(+)

>>> This patch was found by tools developed in the VAMOS project:
>>> http://www4.cs.fau.de/Research/VAMOS/

>> Does that mean that no one actually can hit this in "real life"?  Or is
>> there a valid .config that this solves a problem for?  If so, is it also
>> needed for the 3.4/3.3-stable tree and older ones?

> My tool has generated the attached configuration that exposes this
> compilation failure. I have used kernel v3.2 with Ubuntu's arm
> cross-compiler for the analysis and verification.

    Strange, your .config indicated that DMA driver and MUSB driver into which 
it is linked are build monolithic. You also should use 3.3 series kernel.

> Cheers,
> Reinhard

WBR, Sergei

--
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/