linux-kernel - Re: USB Type-C Port Manager API concern

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0a00a8a0-7955-559e-817e-72781908dd72@gmail.com>
Date:   Fri, 14 Apr 2017 10:30:16 +0200
From:   Mats Karrman <mats.dev.list@...il.com>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Greg KH <gregkh@...uxfoundation.org>,
        Felipe Balbi <felipe.balbi@...ux.intel.com>,
        linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: USB Type-C Port Manager API concern

On 04/14/2017 04:57 AM, Guenter Roeck wrote:

> ... Overall I think there is an assumption in any API that any 
> callback functions provided in a registration call can immediately be 
> called. Otherwise any API would be in trouble. Can you modify your 
> code to not require the port pointer in its callback functions ?

Yes, I have deferred my calls until after the registration function has 
returned which seems only logical. Thanks, Mats