mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.5.67 (and probably earlier)] /proc/dev/net doesnt show all net device
Date: Thu, 1 May 2003 18:31:15 -0700	[thread overview]
Message-ID: <20030501183115.25bb0774.rddunlap@osdl.org> (raw)
In-Reply-To: <200305012018_MC3-1-36FA-118B@compuserve.com>

On Thu, 1 May 2003 20:16:00 -0400 Chuck Ebbert <76306.1226@compuserve.com> wrote:

| Randy Dunlap wrote:
| 
| > The reason that I say that is that I can reproduce this problem on
| > 2.5.68, but only in an xterm or similar window, but when I switch back
| > to a console, the entire device list is displayed.
| 
|  There are strange bugs in the console layer and/or the VGA text console.
| Choosing 34-line text mode results in a 30-line screen that the system
| thinks has 34, with four 'hidden' lines at the bottom (on PCI TNT adapter.)
| Maybe a similar thing is happening in X?

I don't think it's quite as deep down as all that.  I built cat.c with
some additional debugging fprintf()s in it.  When I run it from the
text console, it tells me that the variable <outsize> is 4096
(derived from #define ST_BLKSIZE(statbuf)  <about 4 different #defines>.

However, when run from an X terminal window, it tells me that outsize
is 1024.

I don't have time right now to dig into the 4 #defines for ST_BLKSIZE
to see where the problem is.

Anyway, it looks as though the kernel read function for /proc/net/dev
is filling up cat's buffer and just stopping, which seems OK to me.
Looks like a cat bug IMO, but I haven't finished looking at it.


|  And BTW I found a way to get lots of network devices:
| 
|   1. Load the gre tunneling driver (GRE tunnels over IP)
|   2. ip tunnel add gre1 mode gre remote 127.1.1.1 local 127.0.0.1 dev lo
|   3. Repeat for as many as you like... I can't make the kernel
|      send packets through them but they show up on the list.

OK.  Loading dummy driver multiple times is OK for this.

Later,
--
~Randy

      reply	other threads:[~2003-05-02  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  0:16 Chuck Ebbert
2003-05-02  1:31 ` Randy.Dunlap [this message]

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=20030501183115.25bb0774.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®