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: <20180702131951.GA5786@lst.de>
Date:   Mon, 2 Jul 2018 15:19:51 +0200
From:   Christoph Hellwig <hch@....de>
To:     Fabio Coatti <fabio.coatti@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Christoph Hellwig <hch@....de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: iwlwifi problem with iommu/intel-iommu: Enable
        CONFIG_DMA_DIRECT_OPS=y and clean up intel_{alloc,free}_coherent()

> By reverting this commit the card works again, tested in 4.17.3 . I've noticed 
> that the corresponding amd commit ( b468620f2a1dfdcfddfd6fa54367b8bcc1b51248)
> has been reverted in linus tree (e16c4790de39dc861b749674c2a9319507f6f64f), 
> and 4.16.X stable tree iirc,  but the intel one has not been reverted.
> 
> hw: Lenovo P50 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
> 
> Please let me know if more details are needed, but CC: me as I'm not currently 
> subscribed to LKML.

It probablty is the same issue.  Did you check if you can just revert
the commit cleanly on top of current mainline and that fixes the issue
for you?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ