From: Andy Green <andy@warmcat.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] mac80211: Monitor mode radiotap-based packet injection
Date: Mon, 19 Mar 2007 10:54:58 +0000 [thread overview]
Message-ID: <45FE6C02.5050605@warmcat.com> (raw)
In-Reply-To: <200703190156.07984.flamingice@sourmilk.net>
Michael Wu wrote:
> I've mostly made comments about style issues. There are only comments on the
> first instance of any style problem so please check the rest of the code for
> the same problems.
Thanks for this feedback Michael. I have changed all the style problems
my eyes could see, assisted by visiting every = in the patch.
> Hm, this could be integrated into the switch statement below, but it doesn't
> really matter much.
It's also very handy for...
> Have you looked into padding issues with radiotap headers? For example, if
> there is a 1 byte field which is then followed by a 4 byte field, there needs
> to be 3 bytes of padding after the first field, but if the field after were 2
> bytes long, the padding would only be 1 byte (according to my understanding
> of the radiotap specs).
I googled for radiotap specs but I didn't find anything useful. I added
some small code to enforce the alignment rules you mention above.
I found there was no docs in ./Documentation about 80211, I added a
small explanation and examples about injection including this alignment
Gotcha so the knowledge isn't lost.
> We could avoid this check altogether by spinning this code into a different
> function and setting the xmit handler appropriately depending on if we're
> initializing/switching to a monitor interface or not. Not entirely sure if
> it's worth it, but I thought I'd mention it.
Yes, that method would be marginally better, but there is only a single
int getting tested in the main path and even that is marked up as
unlikely(). So I leave it as it is for now.
-Andy
next prev parent reply other threads:[~2007-03-19 10:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 10:15 [PATCH 0/2] Try #3 Radiotap on Monitor Mode interfaces for rx and tx andy
2007-03-18 10:15 ` [PATCH 1/2] mac80211: Add radiotap support andy
2007-03-18 10:15 ` [PATCH 2/2] mac80211: Monitor mode radiotap-based packet injection andy
2007-03-19 5:55 ` Michael Wu
2007-03-19 10:54 ` Andy Green [this message]
2007-03-19 16:50 ` Michael Wu
2007-03-21 4:12 ` Joerg Mayer
-- strict thread matches above, loose matches on Subject: below --
2007-03-17 10:58 [PATCH 0/2] Radiotap on Monitor Mode interfaces for rx and tx andy
2007-03-17 10:58 ` [PATCH 2/2] mac80211: Monitor mode radiotap-based packet injection andy
2007-03-17 13:59 ` Michael Buesch
2007-03-17 14:58 ` Andy Green
2007-03-17 15:06 ` Michael Buesch
2007-03-17 15:35 ` Andy Green
2007-03-17 21:30 ` Michael Wu
2007-03-17 21:51 ` Michael Wu
2007-03-17 22:09 ` Andy Green
2007-03-17 23:20 ` Michael Wu
2007-03-17 23:26 ` Andy Green
2007-03-18 9:00 ` Andy Green
2007-03-18 10:12 ` Andy Green
2007-03-17 22:05 ` Andy Green
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=45FE6C02.5050605@warmcat.com \
--to=andy@warmcat.com \
--cc=flamingice@sourmilk.net \
--cc=linux-wireless@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).