From: "John W. Linville" <linville@tuxdriver.com>
To: David Miller <davem@davemloft.net>
Cc: j@w1.fi, jouni.malinen@atheros.com, alex.williamson@hp.com,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT]: Networking (WEXT events and 64/32 compat)
Date: Thu, 18 Sep 2008 09:41:13 -0400 [thread overview]
Message-ID: <20080918134112.GB4552@tuxdriver.com> (raw)
In-Reply-To: <20080917.131133.135282530.davem@davemloft.net>
On Wed, Sep 17, 2008 at 01:11:33PM -0700, David Miller wrote:
> From: Jouni Malinen <j@w1.fi>
> Date: Wed, 17 Sep 2008 12:11:28 -0700
>
> > Would it be acceptable to ever enable use of IWEVASSOCREQIE /
> > IWEVSSOCRESPIE in kernel if the workaround were available in new
> > wpa_supplicant versions? Or should we try to add a new WEXT event
> > type that uses fixed size for the length field and then replace the old
> > IWEVCUSTOM with the new type since IWEVCUSTOM does not work with
> > 64/32-bit case (wpa_supplicant just knows how to avoid processing that
> > bogus event data)?
>
> Moving to a new event with a strictly sized datastructure, instead of
> one that has variable sized members like pointers and crap which are
> impossible to compat layer'ify, is indeed my preference.
>
> But in that case, we might as well make nl80211 usable instead.
This is, of course, my opinion as well.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-09-18 13:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 23:46 [GIT]: Networking David Miller
2008-09-05 15:08 ` Alex Williamson
2008-09-05 17:45 ` Linus Torvalds
2008-09-05 18:17 ` John W. Linville
2008-09-09 2:44 ` Jouni Malinen
2008-09-09 2:46 ` David Miller
2008-09-09 2:55 ` Jouni Malinen
2008-09-09 3:43 ` David Miller
2008-09-09 4:05 ` Jouni Malinen
2008-09-09 4:15 ` David Miller
2008-09-09 5:34 ` Jouni Malinen
2008-09-17 19:11 ` [GIT]: Networking (WEXT events and 64/32 compat) Jouni Malinen
2008-09-17 20:11 ` David Miller
2008-09-18 13:41 ` John W. Linville [this message]
2008-09-18 22:13 ` Jouni Malinen
2008-09-09 3:08 ` [GIT]: Networking Alex Williamson
2008-09-09 3:06 ` Jouni Malinen
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=20080918134112.GB4552@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@hp.com \
--cc=davem@davemloft.net \
--cc=j@w1.fi \
--cc=jouni.malinen@atheros.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.