[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bluetooth-dev] PPPD exiting...



Hi Michael,
    what do you mean monitoring here? are you referring to the latest version
stack that ppp died after starting?

Raymond

Michael Frey wrote:

> This is not the case on my end.  PPPD workd great with the pervious version
> of the stack.  If I monitor the processes PPP is started only once then
> dies.
>
> Frustrating...
>
> -----Original Message-----
> From: owner-bluetooth-dev@xxxxxxx.com
> [mailto:owner-bluetooth-dev@xxxxxxx.com]On Behalf Of Gordon McNutt
> Sent: Wednesday, February 14, 2001 12:03 PM
> To: Michael Frey
> Cc: Mikko Rahkonen; bluetooth-dev@xxxxxxx.com
> Subject: Re: [bluetooth-dev] PPPD exiting...
>
> Michael Frey wrote:
>
> >
> > >
> > > After fixing the IP address issue I keep getting "line already open".
> > > Does anybody know, what's the proper way of using the ppp? Here's my
> > > guess:
> > >
>
> We've just had a look at the source with a debug trace. In our version of
> PPP
> (which exhibits this same bug), PPP calls bt_open twice on whatever
> /dev/ttyBT*
> you give it. We've been telling it to use /dev/ttyBT0.
>
> This won't work. If you look in bluetooth.c:bt_register_tty you will see
> that
> only /dev/ttyBTC (alias line 7) can be opened more than once (more on that
> later). That's why the second call to bt_open fails, and pppd then tries
> again,
> and again, and again... Maybe other versions of pppd don't call open twice,
> I'm
> not sure why it thinks it needs to do that.
>
> HAS ANYBODY SEEN PPP WORK OVER 2001/01/08? If so, please post your pppd
> version.
>
> Now, I think we have a bug in bt_open that could cause a kernel panic in
> rare
> circumstances. If two apps both open /dev/ttyBTC (bt_open will not prevent
> this) then the second app's tty->driver_data will not be set. If it
> subsequently calls bt_write_top, the stack will try to use tty->driver_data
> as
> a pointer and will probably cause a kernel panic for dereferencing NULL. If
> I have time I'll try to post a patch to fix this.
>
> --gmcnutt
>
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com
>
> -
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to majordomo@xxxxxxx.com

-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com