public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: maxk@qualcomm.com
Cc: pcg@goof.com, linux-kernel@vger.kernel.org
Subject: Re: 2.4.13-ac5 && vtun not working
Date: Mon, 29 Oct 2001 17:53:12 -0800 (PST)	[thread overview]
Message-ID: <20011029.175312.26299226.davem@redhat.com> (raw)
In-Reply-To: <5.1.0.14.0.20011029174700.08e93090@mail1>
In-Reply-To: <20011030021740.A8708@schmorp.de> <20011030023933.A11774@schmorp.de> <5.1.0.14.0.20011029174700.08e93090@mail1>

   From: Maksim Krasnyanskiy <maxk@qualcomm.com>
   Date: Mon, 29 Oct 2001 17:48:35 -0800

   >On Tue, Oct 30, 2001 at 02:17:40AM +0100, " Marc A. Lehmann " <pcg@goof.com> wrote:
   >> a _lot_ of searching revealed this code fragment:
   >
   >In my usual attempt to generate more traffic, I forgot to mention that I
   >found it in net/core/dev.c ;)
   >
   >(oh, and after reading the comments int hat file, I think that maybe tun.c
   >simply shouldn't call dev_alloc_name...)

   Hmm, let me check that. 
   I was under the assumption that it's dev.c bug :)

Basically, don't pass a string lack one "%d" into dev_alloc_name
because dev_alloc_name() runs sprintf on that string with an
integer argument.

Franks a lot,
David S. Miller
davem@redhat.com

  reply	other threads:[~2001-10-30  1:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  1:17 2.4.13-ac5 && vtun not working Lehmann 
2001-10-30  1:39 ` Lehmann 
2001-10-30  1:48 ` Maksim Krasnyanskiy
2001-10-30  1:53   ` David S. Miller [this message]
2001-10-31  0:05     ` Lehmann 
2001-10-31  8:30       ` David S. Miller
2001-10-31  9:43         ` Lehmann 
2001-10-31 17:55         ` Maksim Krasnyanskiy
2001-11-06 23:32           ` David S. Miller
2001-11-06 23:53           ` Maksim Krasnyanskiy

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=20011029.175312.26299226.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --cc=pcg@goof.com \
    /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