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 13:50:47 +0200	[thread overview]
Message-ID: <1255002647.3713.25.camel@johannes.local> (raw)
In-Reply-To: <1254995514.3713.22.camel@johannes.local>

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

On Thu, 2009-10-08 at 11:51 +0200, Johannes Berg wrote:

> Ok, that's odd. Is it possible that somehow cfg80211 is picking up an
> #ifdef'ed copy of "struct iw_handler_def", and thus the struct it is
> defining is simply too small?

That is apparently what is happening since compat-wireless ships
iw_handler.h. This is wrong, as wext functionality is built into the
kernel image so you can't use a newer header file with it.

johannes

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

  reply	other threads:[~2009-10-08 11:52 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
2009-10-08  6:28     ` Hin-Tak Leung
2009-10-08  9:51       ` Johannes Berg
2009-10-08 11:50         ` Johannes Berg [this message]
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=1255002647.3713.25.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