netdev - Re: confusing comment, explanation of @IFF

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:   Sun, 26 Aug 2018 13:51:44 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     "Robert P. J. Day" <rpjday@...shcourse.ca>
Cc:     Andrew Lunn <andrew@...n.ch>,
        Linux kernel netdev mailing list <netdev@...r.kernel.org>
Subject: Re: confusing comment, explanation of @IFF_RUNNING in if.h

On Sun, 26 Aug 2018 15:20:24 -0400 (EDT)
"Robert P. J. Day" <rpjday@...shcourse.ca> wrote:

> On Sun, 26 Aug 2018, Andrew Lunn wrote:
> 
> > >   i ask since, in my testing, when the interface should have been
> > > up, the attribute file "operstate" for that interface showed
> > > "unknown", and i wondered how worried i should be about that.  
> >
> > Hi Robert
> >
> > You should probably post the driver for review. A well written
> > driver should not even need to care about any of this. phylib and
> > the netdev driver code does all the work. It only gets interesting
> > when you don't have a PHY, e.g. a stacked device, like bonding, or a
> > virtual device like tun/tap.  
> 
>   i wish, but i'm on contract, and proprietary, and NDA and all that.
> so i am reduced to crawling through the code, trying to figure out
> what is misconfigured that is causing all this grief.
> 
> rday
> 

So you expect FOSS developers to help you with proprietary licensed
driver. Good Luck with that.