From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ben Greear <greearb@candelatech.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: /proc/net/dev is funky in 3.3.0
Date: Tue, 03 Apr 2012 08:36:35 +0200 [thread overview]
Message-ID: <1333434995.18626.39.camel@edumazet-glaptop> (raw)
In-Reply-To: <4F7A905B.3080107@candelatech.com>
On Mon, 2012-04-02 at 22:53 -0700, Ben Greear wrote:
> On 04/02/2012 10:43 PM, Eric Dumazet wrote:
> > On Mon, 2012-04-02 at 21:29 -0700, Ben Greear wrote:
> >> Not all entries are shown!
> >>
> >> [root@lanner-i7 lanforge]# cat /proc/net/dev|grep sta59
> >> [root@lanner-i7 lanforge]# ifconfig sta59
> >> sta59 Link encap:Ethernet HWaddr 00:95:95:00:00:3C
> >> inet addr:10.111.9.39 Bcast:10.111.255.255 Mask:255.255.0.0
> >> inet6 addr: fe80::295:95ff:fe00:3c/64 Scope:Link
> >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> >> RX packets:58103 errors:0 dropped:0 overruns:0 frame:0
> >> TX packets:26167 errors:0 dropped:0 overruns:0 carrier:0
> >> collisions:0 txqueuelen:1000
> >> RX bytes:39494634 (37.6 MiB) TX bytes:37095540 (35.3 MiB)
> >>
> >> Thanks,
> >> Ben
> >>
> >
> > Could you post "ip link" result ?
> >
>
> It is below. Looks like /proc/net/dev is missing 6 entries,
> sta69 being one of them. See end of the email for some grep
> and |wc results. Seems easily reproducible, so let me know if
> you want more info.
Hmm, I think I understand, commit f04565ddf52 added a regression here, I
will send a fix.
Thanks
next prev parent reply other threads:[~2012-04-03 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 4:29 /proc/net/dev is funky in 3.3.0 Ben Greear
2012-04-03 5:43 ` Eric Dumazet
2012-04-03 5:53 ` Ben Greear
2012-04-03 6:36 ` Eric Dumazet [this message]
2012-04-03 7:06 ` Eric Dumazet
2012-04-03 7:17 ` Mihai Maruseac
2012-04-03 8:33 ` [PATCH net: fix /proc/net/dev regression Eric Dumazet
2012-04-03 15:36 ` Ben Greear
2012-04-03 15:59 ` Eric Dumazet
2012-04-03 21:25 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1333434995.18626.39.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=greearb@candelatech.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox