linux-kernel - RE: linux-next: build failure after merge of the rdma 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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 5 Dec 2018 12:25:57 +0000
From:   "Guy Levi(SW)" <guyle@...lanox.com>
To:     Jason Gunthorpe <jgg@...lanox.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
CC:     Doug Ledford <dledford@...hat.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Majd Dibbiny <majd@...lanox.com>,
        Leon Romanovsky <leonro@...lanox.com>
Subject: RE: linux-next: build failure after merge of the rdma tree

> 
> Huh. So apparently every compiler that tested this patch (0-day, mine,
> the submitters) optimized this call away because is_atomic_response()
> always returns 0: meaning mlx5_get_atomic_laddr is never callable and
> can be deleted entirely, including the call to mlx5_get_send_wqe.
> 
> Not sure what compiler setup will hit this, but it is clearly wrong
> code..

Flag -o0  ?


> 
> Guy/Leon, please send a fixup.. Maybe just delete all this
> handle_atomics stuff?
> 
> Thanks,
> Jason