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  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:   Tue, 24 Jan 2017 10:59:15 -0800
From:   Florian Fainelli <>
To:     Russell King - ARM Linux <>,
        Andrew Lunn <>,
        Greg KH <>
Cc:, Jason Cooper <>,
        Sebastian Hesselbarth <>,
        Gregory Clement <>,
        Vivien Didelot <>,
        "David S. Miller" <>,
        "moderated list:ARM SUB-ARCHITECTURES" 
        open list <>
Subject: Re: [PATCH net-next v3 06/10] net: dsa: Migrate to

On 01/19/2017 10:12 AM, Florian Fainelli wrote:
> Back to the actual code that triggered this discussion, the whole
> purpose is just a safeguard. Given a device reference, we can assume
> that it is indeed the backing device for a net_device, and we could do a
> to_net_device() right away (and crash if someone did not write correct
> platform_data structures), or, by walking the device tree (the device
> driver model one) we can make sure it does belong in the proper class
> and this is indeed what we think it is.

Greg, did Russell's explanation clarify things, or do you still think
this is completely bogus and we need to re design the whole thing?

Just asking so I can try to resubmit just the preparatory parts or just
the whole thing.

Thank you

Powered by blists - more mailing lists