netdev - Re: IFF_RUNNING without carrier after reboot

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: <20090127163236.GA26065@csclub.uwaterloo.ca>
Date:	Tue, 27 Jan 2009 11:32:36 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	David Miller <davem@...emloft.net>
Cc:	herbert@...dor.apana.org.au, marcel@...tmann.org,
	netdev@...r.kernel.org
Subject: Re: IFF_RUNNING without carrier after reboot

On Sun, Dec 14, 2008 at 11:36:25PM -0800, David Miller wrote:
> From: Herbert Xu <herbert@...dor.apana.org.au>
> Date: Mon, 15 Dec 2008 18:28:00 +1100
> 
> > David Miller <davem@...emloft.net> wrote:
> > >
> > > The RUNNING state has no connection to link presence.
> > > 
> > > It just means that the device has been brought up by a
> > > user configuration command like the ifconfig you ran.
> > > 
> > > It really means nothing else.
> > 
> > Well RUNNING did use to indicate carrier state.  In fact I didn't
> > even know that it had changed until this email :)
> > 
> > This is the changeset which did it:
> 
> Yes, it was a bug and we fixed it more than 2 years ago.
> Thanks for confirming :-)

So the RUNNING flag no longer indicates link state?  Wow that's going to
break some userspace quite badly.

Isn't the UP flag what indicates opstate?

What is the correct way for userspace to detect link state on an
interface?

-- 
Len Sorensen
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html