All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Oliver Hartkopp <oliver@hartkopp.net>,
	Marcel Holtmann <marcel@holtmann.org>,
	Linux Netdev List <netdev@vger.kernel.org>,
	linux-bluetooth@vger.kernel.org,
	"Gustavo F. Padovan" <gustavo@las.ic.unicamp.br>
Subject: Re: [BUG net-2.6] bluetooth/rfcomm : sleeping function called from invalid context at mm/slub.c:1719
Date: Sun, 4 Oct 2009 18:06:35 +0000	[thread overview]
Message-ID: <20091004180635.GA11272@vigoh> (raw)
In-Reply-To: <a8e1da0910032026m66200c08jf9201bbfe34b2f30@mail.gmail.com>


Hi all,

* Dave Young <hidave.darkstar@gmail.com> [2009-10-04 11:26:17 +0800]:

> 
> I can reproduce the bug.
> 
> It's probably caused by the l2cap changes by  Gustavo F. Padovan
> <gustavo@las.ic.unicamp.br>, I didn't see such problem after reverting
> Gustavo's patch series.

I can't reproduce the bug. I'm trying to reproduce it to figure out what of
my changes cause it.

I' running

$ dund -snu -i 00:11:67:CD:0F:CB # to pretend to be dialup/telephone

and on the other side 

$ rfcomm bind 0 00:11:67:CD:0F:CB 1
$ wvdial  # wvdial to /dev/rfcomm0

Both sides are on the same machine. Do you see any real difference
between my try and the call that get the bug?


--
Gustavo F. Padovan

  reply	other threads:[~2009-10-04 18:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02  6:28 [BUG net-2.6] bluetooth/rfcomm : sleeping function called from invalid context at mm/slub.c:1719 Oliver Hartkopp
2009-10-02  6:28 ` Oliver Hartkopp
2009-10-02  9:52 ` Oliver Hartkopp
2009-10-02 11:01 ` Dave Young
2009-10-02 11:01   ` Dave Young
2009-10-02 16:04   ` Oliver Hartkopp
2009-10-02 16:04     ` Oliver Hartkopp
2009-10-03  7:06     ` Dave Young
2009-10-03  9:43       ` Oliver Hartkopp
2009-10-03  9:43         ` Oliver Hartkopp
2009-10-04  3:26         ` Dave Young
2009-10-04  3:26           ` Dave Young
2009-10-04 18:06           ` Gustavo F. Padovan [this message]
2009-10-05  4:08             ` Dave Young
2009-10-05  4:08               ` Dave Young
2009-10-09  0:44             ` Dave Young
2009-10-09  0:44               ` Dave Young
2009-10-10  9:54               ` Oliver Hartkopp
2009-10-10 10:38               ` Marcel Holtmann
2009-10-10 10:38                 ` Marcel Holtmann
2009-10-10 13:45                 ` Dave Young
2009-10-10 13:45                   ` Dave Young
2009-10-11  2:39                   ` Dave Young
2009-10-11  2:39                     ` Dave Young
2009-10-07 17:16     ` Oliver Hartkopp
2009-10-07 17:16       ` Oliver Hartkopp
2009-10-08  1:25       ` Dave Young
2009-10-08  1:25         ` Dave Young

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=20091004180635.GA11272@vigoh \
    --to=gustavo@padovan.org \
    --cc=gustavo@las.ic.unicamp.br \
    --cc=hidave.darkstar@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=oliver@hartkopp.net \
    /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.