public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: linux-kernel@vger.kernel.org
Cc: shemninger@osdl.org
Subject: [RFC] syncppp broken - how to fix?
Date: 03 Mar 2004 13:19:53 -0600	[thread overview]
Message-ID: <1078341592.2118.19.camel@deimos.microgate.com> (raw)

In 2.6.0-test8 a patch from shemninger@osdl.org was
applied to drivers/net/wan/syncppp.c which breaks
syncppp when used with some wan drivers:

drivers/net/wan/cosa.c
drivers/net/wan/hostess_sv11.c
drivers/net/wan/wanpipe_multppp.c
drivers/char/synclink.c
drivers/char/synclinkmp.c
drivers/char/pcmcia/synclink_cs.c

The problem is the addition of a BUG_ON()
line in sppp_attach() which imposes the new
requirement that the net device priv member
be initialized *before* calling sppp_attach().

The priv member is not actually used in
sppp_attach(). The BUG_ON line does a sanity
check which touches priv member, which is not
set prior to calling sppp_attach() by the drivers
listed above.

So should all of the WAN drivers be changed to
accomodate this new requirement (which does not
seem to serve a purpose) ?

Or should the BUG_ON line be removed from
syncppp.c to return it to the original convention?

It seems odd to add a sanity check for a member
that is not used and is not set. It also seems
counter productive to modify multiple drivers
to set this value to accomodate the new sanity check
since that value is still not used in sppp_attach.


-- 
Paul Fulghum
paulkf@microgate.com



             reply	other threads:[~2004-03-03 19:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 19:19 Paul Fulghum [this message]
     [not found] ` <1078341865.2118.22.camel@deimos.microgate.com>
     [not found]   ` <20040303114906.1a4027da@dell_ss3.pdx.osdl.net>
2004-03-03 20:16     ` [RFC] syncppp broken - how to fix? Paul Fulghum

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=1078341592.2118.19.camel@deimos.microgate.com \
    --to=paulkf@microgate.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemninger@osdl.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