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]

Message-ID: <20180826192854.GE7359@lunn.ch>
Date:   Sun, 26 Aug 2018 21:28:54 +0200
From:   Andrew Lunn <andrew@...n.ch>
To:     "Robert P. J. Day" <rpjday@...shcourse.ca>
Cc:     Linux kernel netdev mailing list <netdev@...r.kernel.org>
Subject: Re: confusing comment, explanation of @IFF_RUNNING in if.h

On Sun, Aug 26, 2018 at 03:20:24PM -0400, Robert P. J. Day 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.

I would say proprietary and NDA is causing you all this grief.

There is also the point that if you are not going to contribute the
code to mainline, why should we help you?

The code is GPL after all, so you can post it.

  Andrew