All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eugene Crosser <crosser@average.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: Reproducible kernel oops on PPP session start
Date: Wed, 14 Jan 2004 00:32:03 +0300	[thread overview]
Message-ID: <1074029444.2819.7.camel@pccross.average.org> (raw)
In-Reply-To: <1074022381.2894.5.camel@pegasus>

On Tue, 2004-01-13 at 22:33, Marcel Holtmann wrote:

> actually it is not a wrong owner entry. But the RFCOMM core layer have
> to increment the module reference count of the L2CAP module, when we
> accept a new incoming L2CAP connection. I am not 100% that this is the
> right way to fix this problem, but for me it works. Please check if the
> attached patch helps and don't breaks any other of your setups.

Cool!  At least for me, everything works like a charm.
Thanks a lot, Marcel!

Eugene

  reply	other threads:[~2004-01-13 21:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 11:42 Reproducible kernel oops on PPP session start Eugene Crosser
2004-01-07 12:15 ` [Bluez-devel] " Marcel Holtmann
2004-01-07 13:57   ` Eugene Crosser
2004-01-10 12:00     ` Eugene Crosser
2004-01-10 12:11       ` Eugene Crosser
2004-01-11 14:59         ` Marcel Holtmann
2004-01-12  6:33           ` Eugene Crosser
2004-01-12 13:22             ` Marcel Holtmann
2004-01-12 14:52               ` Eugene Crosser
2004-01-12 15:15                 ` Marcel Holtmann
2004-01-12 21:22                   ` Eugene Crosser
2004-01-12 21:35                     ` Marcel Holtmann
2004-01-12 22:02                       ` Eugene Crosser
2004-01-13 17:32                         ` Marcel Holtmann
2004-01-13 19:33                           ` Marcel Holtmann
2004-01-13 21:32                             ` Eugene Crosser [this message]
2004-01-13 23:14                               ` Marcel Holtmann
2004-01-07 14:05   ` Edd Dumbill

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=1074029444.2819.7.camel@pccross.average.org \
    --to=crosser@average.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.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 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.