From: Johannes Berg <johannes@sipsolutions.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Laurent Riffard <laurent.riffard@free.fr>,
linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: [PATCH] sotftmac: fix a slab corruption in WEP restricted key association
Date: Fri, 13 Oct 2006 11:04:51 +0200 [thread overview]
Message-ID: <1160730291.2697.10.camel@ux156> (raw)
In-Reply-To: <452D8D83.60908@gentoo.org>
On Wed, 2006-10-11 at 20:34 -0400, Daniel Drake wrote:
> > - is_shared_response ? 0 : 1 + 1 + net->challenge_len
> > + (is_shared_response ? 1 + 1 + net->challenge_len : 0)
Good catch. We should send this to -stable too I think. Mind reposting
the patch in an applicable format to Daniel, netdev, john, -stable (and
possibly me)? Quoted isn't too useful :)
Oh and you can add
Acked-by: Johannes Berg <johannes@sipsolutions.net>
johannes
next prev parent reply other threads:[~2006-10-13 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <452D6D80.3020005@free.fr>
2006-10-12 0:34 ` [PATCH] sotftmac: fix a slab corruption in WEP restricted key association Daniel Drake
2006-10-13 9:04 ` Johannes Berg [this message]
2006-10-13 12:08 ` Daniel Drake
2006-10-13 12:12 ` Johannes Berg
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=1160730291.2697.10.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=dsd@gentoo.org \
--cc=laurent.riffard@free.fr \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).