From: Jouni Malinen <jkmaline@cc.hut.fi>
To: Pavel Roskin <proski@gnu.org>
Cc: netdev@vger.kernel.org, hostap@shmoo.com,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] hostap_plx: fix CIS verification
Date: Tue, 24 Oct 2006 18:44:48 -0700 [thread overview]
Message-ID: <20061025014447.GA6121@jm.kir.nu> (raw)
In-Reply-To: <1161737289.29298.6.camel@dv>
On Tue, Oct 24, 2006 at 08:48:09PM -0400, Pavel Roskin wrote:
> I don't have Coverity to check, and I think the results of Coverity were
> misinterpreted. It doesn't know anything about CIS structure. Anyway,
> let me just check Jouni's suggestion on a real PLX card.
It doesn't need to know anything about the CIS structure. The driver
must not be allowed to run over a buffer even if given an invalid CIS
data.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2006-10-25 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 22:20 [PATCH] hostap_plx: fix CIS verification Pavel Roskin
2006-10-21 1:19 ` Jouni Malinen
2006-10-25 0:37 ` John W. Linville
2006-10-25 0:48 ` Pavel Roskin
2006-10-25 1:44 ` Jouni Malinen [this message]
2006-10-25 2:12 ` Pavel Roskin
2006-10-25 2:31 ` Jouni Malinen
2006-10-25 2:41 ` [PATCH FIXED] " Pavel Roskin
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=20061025014447.GA6121@jm.kir.nu \
--to=jkmaline@cc.hut.fi \
--cc=hostap@shmoo.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.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).