public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	linux-wireless@vger.kernel.org
Subject: Re: NULL pointer deref at wext ioctl (Re: [PATCH] compat-2.6: adding  ethtool.h to compat-2.6.31.h)
Date: Thu, 08 Oct 2009 00:01:26 +0200	[thread overview]
Message-ID: <1254952886.3713.4.camel@johannes.local> (raw)
In-Reply-To: <3ace41890910071228i786d4097w69dc7a3dfeb64afe@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]

On Wed, 2009-10-07 at 20:28 +0100, Hin-Tak Leung wrote:
> On Wed, Oct 7, 2009 at 8:16 PM, Hin-Tak Leung <hintak.leung@gmail.com> wrote:
> 
> > It is probably just a transient problem with recent activities - I had
> > a NULL pointer deref from loading rtl8187 of compat-wireless
> > v2.6.32-rc3-39563-g98c2609 -
> >
> > BUG: unable to handle kernel NULL pointer dereference at 000000000000003d
> > IP: [<ffffffff8147822c>] wext_ioctl_dispatch+0xd9/0x180
> > PGD 61c2b067 PUD 6246f067 PMD 0
> > Oops: 0000 [#1] SMP
> > ...
> > Call Trace:
> >  [<ffffffff814783f5>] wext_handle_ioctl+0x4d/0x98
> >  [<ffffffff813e53a5>] dev_ioctl+0x625/0x662
> >  [<ffffffff813cfa45>] sock_ioctl+0x225/0x248
> >  [<ffffffff811237a3>] vfs_ioctl+0x31/0xaa
> >  [<ffffffff811e1801>] ? security_d_instantiate+0x37/0x4d
> >  [<ffffffff81123c88>] do_vfs_ioctl+0x46c/0x4c3
> >  [<ffffffff81123d44>] sys_ioctl+0x65/0x9c
> >  [<ffffffff81012082>] system_call_fastpath+0x16/0x1b
> >
> > I'm sure whatever changes made this happen will go away soon, so I'll
> > just re-try in a few days... but if anybody knows what commit causes
> > this (and what fixes it!), I'd like to know.
> >
> 
> Hiya, It looks like I last used compat-wireless successfully was on
> 25th (I am not saying it breaks after - I just haven't tried until
> yesterday, possibly), and most of the recent changes are per-driver,
> but there is a big code drop from Johannes dated 27th on 'wext:
> refactor' . Changes from that or dependent changes?

Probably -- but I don't see this problem on stock kernel and I'm not
sure what could be causing it for compat-wireless.

This will be the old copy of wext_ioctl_dispatch. It'd certainly help to
get disassembly/the source line of the oops.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 19:16 NULL pointer deref at wext ioctl (Re: [PATCH] compat-2.6: adding ethtool.h to compat-2.6.31.h) Hin-Tak Leung
2009-10-07 19:28 ` Hin-Tak Leung
2009-10-07 22:01   ` Johannes Berg [this message]
2009-10-08  6:28     ` Hin-Tak Leung
2009-10-08  9:51       ` Johannes Berg
2009-10-08 11:50         ` Johannes Berg
2009-10-08 13:43           ` Luis R. Rodriguez
2009-10-08 14:28             ` Luis R. Rodriguez
2009-10-08 14:43               ` John W. Linville
2009-10-08 14:59                 ` Luis R. Rodriguez
2009-10-08 23:22             ` Hin-Tak Leung
2009-10-09  0:14               ` Luis R. Rodriguez
2009-10-09  8:05                 ` Johannes Berg
2009-10-13 21:04                   ` Luis R. Rodriguez

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=1254952886.3713.4.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    /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