All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM REPORT 2.4.20-rc1: sundance.c
Date: Thu, 31 Oct 2002 16:04:10 -0500	[thread overview]
Message-ID: <3DC19ACA.9030906@pobox.com> (raw)
In-Reply-To: 20021031173834.4514603a.skraw@ithnet.com

Stephan von Krawczynski wrote:

>Hello all,
>
>I'd like to point out that (at least) the network driver sundance.c has weird
>flaws when trying to use more than MAX_UNITS (8) cards at the same time. Since
>

Smileys nonwithstanding, you need to include far more information

Please define "weird flaws"... explicitly.

>this driver can be used for DFE-580TX 4 port network card it is really easy to
>get more than 8 ports :-)
>In fact the driver does check against MAX_UNITS, but does _not_ fail if you go
>through the roof. Instead you can expect really interesting ifconfig-outputs
>;-)
>IMHO it should check and fail. I wonder what other card drivers do in such a
>case ...
>  
>

Other card drivers handle this case just fine.  The expected behavior is 
that module options will only support up to MAX_UNITS of certain 
arguments, but beyond that nothing is affected at all.

    Jeff





  parent reply	other threads:[~2002-10-31 20:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 16:38 PROBLEM REPORT 2.4.20-rc1: sundance.c Stephan von Krawczynski
2002-10-31 17:30 ` PROBLEM REPORT 2.4.20-rc1: sundance.c (OT: userspace) Stephan von Krawczynski
2002-10-31 21:04 ` Jeff Garzik [this message]
2002-11-02 14:54   ` PROBLEM REPORT 2.4.20-rc1: sundance.c Stephan von Krawczynski

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=3DC19ACA.9030906@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.