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, 12 Jun 2017 14:44:04 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     gregkh <gregkh@...uxfoundation.org>
Cc:     "kernelci.org bot" <bot@...nelci.org>,
        Tom Gall <tom.gall@...aro.org>,
        Sumit Semwal <sumit.semwal@...aro.org>,
        Amit Pundir <amit.pundir@...aro.org>,
        Arnd Bergmann <arnd.bergmann@...aro.org>,
        Anmar Oueja <anmar.oueja@...aro.org>,
        Alexander Sverdlin <alexander.sverdlin@...il.com>,
        Vinod Koul <vinod.koul@...el.com>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        dmaengine@...r.kernel.org
Subject: Re: stable-rc/linux-4.4.y build: 199 builds: 13 failed, 186 passed,
 13 errors, 4 warnings (v4.4.71-63-g409ebd600970)

On Mon, Jun 12, 2017 at 1:59 PM, gregkh <gregkh@...uxfoundation.org> wrote:
> On Mon, Jun 12, 2017 at 01:28:48PM +0200, Arnd Bergmann wrote:
>> >>       1  drivers/dma/ep93xx_dma.c:1357:9: error: 'struct dma_device' has no member named 'device_synchronize'
>> >
>> > The error was introudced by the backport of 98f9de366fcc ("dmaengine: ep93xx:
>> > Don't drain the transfers in terminate_all()"), which requires the dmaengine
>> > synchronize callback.
>> >
>> > device_synchronize was introduced by b36f09c3c441 ("dmaengine: Add transfer
>> > termination synchronization support") in linux-4.5. That is not a
>> > bugfix but would
>> > cleanly apply on top of 4.4 and has no dependencies or side-effects.
>> >
>> > We can either revert 98f9de366fcc or backport b36f09c3c441.
>
> I'll just go drop 98f9de366fcc as that's best here.  I don't think
> anyone really cares about this driver in 4.4, and if they do, then they
> can speak up :)

Sounds fine. ep93xx was once an important platform and the chips are still
being sold, but I guess not many users remain. Alexander Sverdlin just stepped
up as the platform maintainer, so he can decide whether he wants his fix
in linux-4.4.y.

        Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ