linux-kernel - Re: ION changes in staging for 4.12

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] [day] [month] [year] [list]

Message-ID: <ad7e04b5-8cab-601c-4d17-873a8ded508c@redhat.com>
Date:   Tue, 9 May 2017 08:04:24 -0700
From:   Laura Abbott <labbott@...hat.com>
To:     John Stultz <john.stultz@...aro.org>
Cc:     Sumit Semwal <sumit.semwal@...aro.org>,
        Greg KH <gregkh@...uxfoundation.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: ION changes in staging for 4.12

On 05/08/2017 05:18 PM, John Stultz wrote:
> Hey Laura,
>    Wanted to check in on ION changes that landed in the staging merge
> for 4.12...
> 
> So with these changes, I can no longer get HiKey to boot to graphics.
> We had previously been using the dummy ion driver, and I've added the
> new config entries for the various standard heaps, but it seems like
> things still aren't working.
> 
> Was curious if this is an expected hard ABI break, or if I'm missing
> something, and if so, maybe how the resulting patches were tested?  Is
> there any sort of transition document to help folks figure out what
> changes they might need to make to support the new ABI?
> 
> thanks
> -john
> 

Yes, this was intentionally decided to be ABI breaking. It turned out
to be too much of a pain to be backwards compatible and I'm not too
surprised things have broken (sorry...). What I suspect is happening
is that the heap ids no longer match so userspace needs to call the
query ioctl to get the heap information. This is also lacking in
documentation at the moment (sorry again) but should be coming soon.

Thanks,
Laura