From: Stefan Seyfried <seife@suse.de>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Rfcomm kernel crashes (2.6.18.2)
Date: Mon, 20 Nov 2006 10:26:22 +0100 [thread overview]
Message-ID: <20061120092622.GF4941@suse.de> (raw)
In-Reply-To: <1164011287.28397.9.camel@localhost>
On Mon, Nov 20, 2006 at 09:28:07AM +0100, Marcel Holtmann wrote:
> so you have something to reproduce this. That is good. Please try out
> the attached patch and report back if it fixes this for you.
just in case this is supposed to go in...
> diff --git a/net/bluetooth/rfcomm/tty.c b/net/bluetooth/rfcomm/tty.c
> index b8e3a5f..46c03f8 100644
> --- a/net/bluetooth/rfcomm/tty.c
> +++ b/net/bluetooth/rfcomm/tty.c
> @@ -915,12 +915,14 @@ static void rfcomm_tty_unthrottle(struct
> static int rfcomm_tty_chars_in_buffer(struct tty_struct *tty)
> {
> struct rfcomm_dev *dev =3D (struct rfcomm_dev *) tty->driver_data;
> - struct rfcomm_dlc *dlc =3D dev->dlc;
> =
> BT_DBG("tty %p dev %p", tty, dev);
dev used
=
> - if (!skb_queue_empty(&dlc->tx_queue))
> - return dlc->mtu;
> + if (!dev || !dev->dlc)
dev checked.
> + return 0;
> +
> + if (!skb_queue_empty(&dev->dlc->tx_queue))
> + return dev->dlc->mtu;
> =
> return 0;
> }
> @@ -928,11 +930,12 @@ static int rfcomm_tty_chars_in_buffer(st
> static void rfcomm_tty_flush_buffer(struct tty_struct *tty)
> {
> struct rfcomm_dev *dev =3D (struct rfcomm_dev *) tty->driver_data;
> - if (!dev)
> - return;
> =
> BT_DBG("tty %p dev %p", tty, dev);
dev used
=
> + if (!dev || !dev->dlc)
dev checked....
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-20 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 2:27 [Bluez-devel] Rfcomm kernel crashes (2.6.18.2) Axel Ruder
2006-11-20 8:28 ` Marcel Holtmann
2006-11-20 9:26 ` Stefan Seyfried [this message]
2006-11-20 9:35 ` Marcel Holtmann
2006-11-20 10:25 ` Stefan Seyfried
-- strict thread matches above, loose matches on Subject: below --
2006-11-24 4:09 Axel Ruder
2006-11-28 2:06 Axel Ruder
2006-11-28 4:18 ` Marcel Holtmann
2006-11-28 4:21 ` Marcel Holtmann
2006-12-04 23:19 ` Axel Ruder
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=20061120092622.GF4941@suse.de \
--to=seife@suse.de \
--cc=bluez-devel@lists.sourceforge.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