linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: Weedy <weedy2887@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath5k past 2.6.30 breaks monitor mode (and thus the aircrack suite)
Date: Sun, 23 May 2010 20:12:21 +0200	[thread overview]
Message-ID: <AANLkTimH3p-dBA_6ee2a0iCnPDhtPZONzCEVkzMHrUWo@mail.gmail.com> (raw)
In-Reply-To: <AANLkTim4zLxIQH2r76WZRh9kNigVNAngcK1d9-Cu65Ag@mail.gmail.com>

2010/5/23 Weedy <weedy2887@gmail.com>:
> 2010/5/17 Gábor Stefanik <netrolller.3d@gmail.com>:
>> What about cutting down the kernel to the absolute minimum required by
>> your machine?
>>
>> Also, Kbuild supports incremental builds as long as you do not "make
>> clean" before builds.
>>
> I just finished the cycle (told you it would take forever on this
> crapbook) and this  is what I got. To be sure I have done multiple
> boots with vmlinuz-2.6.31-rc5fffffffff-01634-geadac6b and
> vmlinuz-2.6.31-rc5fffffffff-01635-g56d1de0 and confirmed it broken.
> Patching todays compat-wireless tar with the output of "git diff
> 56d1de0a21db28e41741cfa0a66e18bc8d920554
> 56d1de0a21db28e41741cfa0a66e18bc8d920554^ >fffffffff.diff " restores
> expected functionality (Does this mean I get my name in the kernel
> log? :D ).
>
> $ git bisect bad
> 56d1de0a21db28e41741cfa0a66e18bc8d920554 is the first bad commit
> commit 56d1de0a21db28e41741cfa0a66e18bc8d920554
> Author: Bob Copeland <me@bobcopeland.com>
> Date:   Mon Aug 24 23:00:30 2009 -0400
>
>    ath5k: clean up filter flags setting
>
>    The maze of if() statements in configure_filter is confusing.
>    Reorganizing it as a switch statement makes it more apparent what
>    is going on and reveals several suspicious settings.  This has no
>    functional changes, though it does remove some redundant flags
>    that are set earlier.
>
>    Also now that we can sleep, protect sc->filter_flags with the
>    sc lock.
>
>    Signed-off-by: Bob Copeland <me@bobcopeland.com>
>    Signed-off-by: John W. Linville <linville@tuxdriver.com>
>
> :040000 040000 1ca00241b99b379f192c1ade63c082955c7dda69
> 1a19187e11210e3c66c224dba62a1896c46d0114 M      drivers
>

Certainly a possible cause. Chances are some of the "redundant" flags
weren't so redundant at all...

However, the original code was wrong too - I highly doubt we can rely
on sc->opmode to set monitor mode filter flags. I will look into this
when I get to my Linux box again.

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

  parent reply	other threads:[~2010-05-23 18:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-16 20:41 ath5k past 2.6.30 breaks monitor mode (and thus the aircrack suite) Weedy
2010-05-16 21:49 ` Gábor Stefanik
2010-05-17  6:38   ` Weedy
2010-05-17 11:21     ` Gábor Stefanik
     [not found]       ` <AANLkTikRt1fUgngBQxEoEFe1VDrYVFRAoMSR53et7gxf@mail.gmail.com>
     [not found]         ` <AANLkTim-A_TWT-flrW88gJGan47Xhm7llyrQE3ehDKU6@mail.gmail.com>
     [not found]           ` <AANLkTim4zLxIQH2r76WZRh9kNigVNAngcK1d9-Cu65Ag@mail.gmail.com>
2010-05-23 18:12             ` Gábor Stefanik [this message]
2010-05-23 18:17               ` Gábor Stefanik
     [not found]                 ` <AANLkTimYeL4KQozuTl4le9WUpObsjwp0YAx7eAYq6MBr@mail.gmail.com>
2010-05-25  2:23                   ` Gábor Stefanik
2010-05-25 13:30                     ` Weedy
2010-05-25 14:53                       ` Bob Copeland
2010-05-25 22:59                         ` Gábor Stefanik
2010-05-26 12:43                           ` Bob Copeland
2010-05-26 21:47                             ` Weedy
2010-05-27  3:49                             ` Richard Farina
2010-05-27 14:31                               ` Bob Copeland
2010-05-27 17:40                                 ` Weedy
2010-05-27 18:31                                   ` Bob Copeland
2010-05-27 18:41                                     ` John W. Linville
2010-05-28  3:39                                       ` Weedy
2010-05-28 18:16                                 ` Richard Farina

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=AANLkTimH3p-dBA_6ee2a0iCnPDhtPZONzCEVkzMHrUWo@mail.gmail.com \
    --to=netrolller.3d@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=weedy2887@gmail.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 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).