From: Pavel Roskin <proski@gnu.org>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: Kalle Valo <kvalo@adurom.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, johill@sipsolutions.net,
reinette.chatre@intel.com, Adel Gadllah <adel.gadllah@gmail.com>
Subject: Re: [PATCH] iwlagn: Change the TPT calculations sanity-check to WARN_ON
Date: Mon, 03 May 2010 17:01:44 -0400 [thread overview]
Message-ID: <1272920504.4907.5.camel@mj> (raw)
In-Reply-To: <AANLkTimf_aZyUSZInOzUPZ8KRR6oDs3Re4pSGGn541fM@mail.gmail.com>
On Mon, 2010-05-03 at 22:48 +0200, Gábor Stefanik wrote:
> One exception I can think of: major misconfiguration can cause a
> wireless device to DMA data into sensitive memory locations. When
> evidence of this is detected, it might make sense to BUG_ON()
> (especially if the bogus DMA operations can be exploited remotely to
> overwrite arbitrary memory addresses). However, in that case, the
> attacker may have already overwritten panic() with malicious code as
> well, so even this case doesn't hold.
And then there is a case when encryption fails and there is a risk of
transmitting data without encryption or accepting data without
verification.
But generally, I agree.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-05-03 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 17:25 [PATCH] iwlagn: Change the TPT calculations sanity-check to WARN_ON John W. Linville
2010-05-03 17:48 ` reinette chatre
2010-05-03 17:55 ` [PATCH] iwlwifi: recalculate average tpt if not current reinette chatre
2010-05-06 16:11 ` reinette chatre
2010-05-06 18:22 ` John W. Linville
2010-05-06 18:50 ` reinette chatre
2010-05-03 20:29 ` [PATCH] iwlagn: Change the TPT calculations sanity-check to WARN_ON Kalle Valo
2010-05-03 20:48 ` Gábor Stefanik
2010-05-03 21:01 ` Pavel Roskin [this message]
2010-05-03 21:10 ` Adel Gadllah
2010-05-03 21:20 ` Gábor Stefanik
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=1272920504.4907.5.camel@mj \
--to=proski@gnu.org \
--cc=adel.gadllah@gmail.com \
--cc=johill@sipsolutions.net \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.com \
--cc=reinette.chatre@intel.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 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.