netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Young <hidave.darkstar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Oliver Hartkopp <oliver-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
Cc: Alan Cox <alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>,
	Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>,
	Linux Netdev List
	<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: tty_register_device NULL pointer dereference in 2.6.31-rc4
Date: Fri, 31 Jul 2009 18:10:21 +0800	[thread overview]
Message-ID: <a8e1da0907310310h483cedeeg433947d51345246c@mail.gmail.com> (raw)
In-Reply-To: <20090731093949.GA4867@darkstar>

On Fri, Jul 31, 2009 at 5:39 PM, Dave Young<hidave.darkstar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> On Thu, Jul 30, 2009 at 12:05:55PM +0200, Oliver Hartkopp wrote:
>> Dave Young wrote:
>> > On Wed, Jul 29, 2009 at 10:00 PM, Oliver Hartkopp<oliver@hartkopp.net> wrote:
>> >> Hi Dave,
>> >>
>> >> i got it again - even with your patch (that's why it's 2.6.31-rc4-dirty in the
>> >> attached screenshot).
>> >
>> > Weird, the oops occurs between sock init and tty init routines. Could
>> > you tell your bluez version and your configuration?
>> >
>>
>> No problem:
>
> Thanks.
>
> It's still reasonable, after rfcomm sock layer initialized, userspace do sock ioctl callback but tty layer was not initilized yet at this time.
>
> Could you confirm it by applying following debug patch on top of my previous patch? if you get more oops with it then above reason will be right.
>
> --- linux-2.6.orig/net/bluetooth/rfcomm/core.c  2009-07-31 17:14:07.000000000 +0800
> +++ linux-2.6/net/bluetooth/rfcomm/core.c       2009-07-31 17:30:39.000000000 +0800
> @@ -36,6 +36,7 @@
>  #include <linux/net.h>
>  #include <linux/mutex.h>
>  #include <linux/kthread.h>
> +#include <linux/nmi.h>
>
>  #include <net/sock.h>
>  #include <asm/uaccess.h>
> @@ -2080,7 +2081,7 @@ static CLASS_ATTR(rfcomm_dlc, S_IRUGO, r
>  /* ---- Initialization ---- */
>  static int __init rfcomm_init(void)
>  {
> -       int ret;
> +       int ret, i;
>
>        l2cap_load();
>
> @@ -2088,6 +2089,12 @@ static int __init rfcomm_init(void)
>        if (ret)
>                goto out_sock;
>
> +       /* delay 5 seconds to trigger the tty bug */
> +       for (i = 0; i < 50; i++) {
> +               touch_nmi_watchdog();
> +               mdelay(100);

Hi, for this case, msleep is better, you can just replace the above
two lines with msleep(100)

> +       }
> +
>        ret = rfcomm_init_ttys();
>        if (ret)
>                goto out_tty;
>



-- 
Regards
dave

  reply	other threads:[~2009-07-31 10:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-25 10:01 tty_register_device NULL pointer dereference in 2.6.31-rc4 Oliver Hartkopp
2009-07-25 10:50 ` Alan Cox
2009-07-25 11:07   ` Marcel Holtmann
2009-07-25 12:10     ` Alan Cox
     [not found]       ` <20090725131046.0f076f37-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org>
2009-07-27  9:59         ` Dave Young
2009-07-27 11:12           ` Oliver Hartkopp
2009-07-27 11:39             ` Oliver Hartkopp
     [not found]               ` <4A6D91D7.6030204-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2009-07-27 14:07                 ` Dave Young
2009-07-29 14:00                   ` Oliver Hartkopp
2009-07-30  9:15                     ` Dave Young
2009-07-30 10:05                       ` Oliver Hartkopp
     [not found]                         ` <4A717083.5090101-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2009-07-31  9:39                           ` Dave Young
2009-07-31 10:10                             ` Dave Young [this message]
2009-07-31 11:20                               ` Oliver Hartkopp
     [not found]                                 ` <4A72D373.7080802-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2009-08-01  3:17                                   ` Dave Young
2009-08-01  9:15                                     ` Oliver Hartkopp
2009-08-01  9:21                                     ` Oliver Hartkopp
2009-08-01  9:32                                       ` Dave Young
2009-08-03 12:03                                         ` Oliver Hartkopp

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=a8e1da0907310310h483cedeeg433947d51345246c@mail.gmail.com \
    --to=hidave.darkstar-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=alan-qBU/x9rampVanCEyBjwyrvXRex20P6io@public.gmane.org \
    --cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marcel-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=oliver-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.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;
as well as URLs for NNTP newsgroup(s).