netdev - Re: [PATCH] Re: IFF_LOWER_UP does not fit in ifr

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: <20090611.205735.120685201.davem@davemloft.net>
Date:	Thu, 11 Jun 2009 20:57:35 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	john.dykstra1@...il.com
Cc:	akpm@...ux-foundation.org, fredrik.arnerup@...eware.tv,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] Re: IFF_LOWER_UP does not fit in ifr_flags

From: John Dykstra <john.dykstra1@...il.com>
Date: Fri, 05 Jun 2009 16:24:07 +0000

> On Fri, 2009-05-29 at 20:50 -0700, Andrew Morton wrote:
>> On Thu, 28 May 2009 14:59:05 +0200 "Fredrik Arnerup" <fredrik.arnerup@...eware.tv> wrote:
>> 
>> > Documentation/networking/operstates.txt (and netdevice(7)) claims that
>> > the flags IFF_LOWER_UP, IFF_DORMANT and IFF_ECHO can be read from user space
>> > using ioctl() with SIOCGIFFLAGS. Looking in include/linux/if.h however,
>> > the flags are returned in a struct ifreq in the field ifr_flags which
>> > is declared as a short, while the flags are defined as:
>> > 
>> > #define IFF_LOWER_UP    0x10000         /* driver signals L1 up         */
>> > #define IFF_DORMANT     0x20000         /* driver signals dormant       */
>> > #define IFF_ECHO        0x40000         /* echo sent packets            */
> 
> [PATCH] net core: Some interface flags not returned by SIOCGIFFLAGS
 ...
> Reported-by:  "Fredrik Arnerup" <fredrik.arnerup@...eware.tv>
> Signed-off-by: John Dykstra <john.dykstra1@...il.com>

Applied, thanks!
--
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