From: Jean Tourrilhes <jt@hpl.hp.com>
To: Michal Rokos <michal@rokos.info>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [IrDA] Oops with NULL deref in irda_device_set_media_busy
Date: Tue, 5 Apr 2005 10:01:02 -0700 [thread overview]
Message-ID: <20050405170102.GD10447@bougret.hpl.hp.com> (raw)
In-Reply-To: <200504051102.27533.michal@rokos.info>
On Tue, Apr 05, 2005 at 11:02:26AM +0200, Michal Rokos wrote:
> Hello,
>
> I've problems with IrDA - when debug is off, I'm getting oops for obvious
> reason...
> (I don't have a log, this is just rewrite from screen:
> EIP: irda_device_set_media_busy+0x15/0x40 [irda]
> ali_ircc_sir_receive+0x4a/0x70
> ali_ircc_sir_interrupt+0x66/0x70
> ali_ircc_interrupt+0x5e/0x80
> .....
> )
> When I turn debug on, I get just
> Assertion failed! net/irda/irda_device.c:irda_device_set_media_busy:128
> self != NULL
>
> The obvious reason is that I don't have irlap module in that inits
> dev->atalk_ptr, so I'm getting assertion exception in irda_device.c:489.
I'm unclear here. The default IrDA stack intitialise properly
dev->atalk_ptr in every case, and is not expected to work if you
don't. I don't understand why dev->atalk_ptr would not be initialised,
is it something you did or something specific to the mr kernel (I only
test mainline kernels).
> A few info that could be handy:
>
> $ uname -a # It's yesterday bk snapshot
> Linux csas 2.6.12-rc1-mr #14 Mon Apr 4 13:42:14 CEST 2005 i686 GNU/Linux
Have fun...
Jean
next prev parent reply other threads:[~2005-04-05 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 9:02 Michal Rokos
2005-04-05 17:01 ` Jean Tourrilhes [this message]
2005-04-06 7:22 ` Michal Rokos
2005-04-06 16:49 ` Jean Tourrilhes
2005-04-07 6:22 ` Michal Rokos
2005-04-07 16:34 ` Jean Tourrilhes
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=20050405170102.GD10447@bougret.hpl.hp.com \
--to=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@rokos.info \
/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
all inboxes | Powered by JetHome®