public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marcel Holtmann <marcel@holtmann.org>
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:10:46 +0100	[thread overview]
Message-ID: <20090725131046.0f076f37@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1248520053.28545.156.camel@violet>

> > 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.

The tty layer doesn't care about the struct device really. Nothing there
has changed. The NULL passed appears to be the driver argument.

  reply	other threads:[~2009-07-25 12: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 [this message]
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-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 10:10                       ` Dave Young
2009-07-31 11:20                         ` Oliver Hartkopp
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=20090725131046.0f076f37@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox