From: Marcel Holtmann <marcel@holtmann.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Oliver Hartkopp <oliver@hartkopp.net>,
Linux Netdev List <netdev@vger.kernel.org>,
linux-bluetooth@vger.kernel.org
Subject: Re: tty_register_device NULL pointer dereference in 2.6.31-rc4
Date: Sat, 25 Jul 2009 13:07:33 +0200 [thread overview]
Message-ID: <1248520053.28545.156.camel@violet> (raw)
In-Reply-To: <20090725115011.7ddf8d00@lxorguk.ukuu.org.uk>
Hi Alan,
> > this morning i got a NULL pointer dereference in tty_register_device() that
> > looked similar to the one, i posted here on 03-jun-2009:
> >
> > http://marc.info/?l=linux-bluetooth&m=124404919324542&w=2
> >
> > As the boot sequence stopped after this point, i was only able to take a
> > picture of it - see attached jpg.
> >
> > I was able to shut down the system gracefully by pressing the power button.
> >
> > The problem emerges really seldom.
> >
> > Any idea?
>
> tty_register_device appears to have been called with a NULL pointer. Not
> sure why however.
if that is the pointer for the struct device, then that used to be fine
in the past. Not all RFCOMM device have a parent when they are created.
Regards
Marcel
next prev parent reply other threads:[~2009-07-25 11:07 UTC|newest]
Thread overview: 26+ 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 [this message]
2009-07-25 12:10 ` Alan Cox
2009-07-25 12:10 ` Alan Cox
2009-07-27 9:59 ` Dave Young
2009-07-27 9:59 ` Dave Young
2009-07-27 11:12 ` Oliver Hartkopp
2009-07-27 11:39 ` Oliver Hartkopp
2009-07-27 14:07 ` Dave Young
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
2009-07-31 9:39 ` Dave Young
2009-07-31 9:39 ` Dave Young
2009-07-31 10:10 ` Dave Young
2009-07-31 10:10 ` Dave Young
2009-07-31 11:20 ` Oliver Hartkopp
2009-08-01 3:17 ` Dave Young
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: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=1248520053.28545.156.camel@violet \
--to=marcel@holtmann.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-bluetooth@vger.kernel.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.