From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: sedat.dilek@gmail.com, David Miller <davem@davemloft.net>,
Stephen Rothwell <sfr@canb.auug.org.au>,
wireless <linux-wireless@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ]
Date: Tue, 6 Aug 2013 23:56:57 +0200 [thread overview]
Message-ID: <20130806215657.GA16410@order.stressinduktion.org> (raw)
In-Reply-To: <1375825538.10459.1.camel@jlt4.sipsolutions.net>
On Tue, Aug 06, 2013 at 11:45:38PM +0200, Johannes Berg wrote:
> On Tue, 2013-08-06 at 23:40 +0200, Sedat Dilek wrote:
>
> > > Does the problem occur on client or server side? AFAICT, hostapd as well
> > > as wpa_supplicant use AF_PACKET.
> > >
> > > The tricky thing is, these patches are meant to *loosen* the
> > > restrictions in af_packet.c, so *should* not be harmful. So either my
> > > patches create a side effect I did not foresee, or it's something nasty
> > > (too much delay introduced by calling eth_type_trans() or so).
>
> > By reverting the culprit commit my network/wifi is fine, again.
> > See also attached patch with changelog.
>
> I think skb->protocol is probably getting set up wrong, and just putting
> back the last two lines
>
> skb->protocol = proto;
> skb->dev = dev;
>
> is probably sufficient to fix wifi. If skb->protocol isn't set to
> ETH_P_PAE, then we'd drop the packet in the wifi stack - might be worth
> printing out what it's set to at the point where the skb->protocol
> assignment above was removed.
>
> I'm trying to wrap my head around all this right now but I don't yet see
> how the code after the patch would not get skb->protocol correct.
Has anybody tested plain ethernet? I have a malfunctioning dhclient on
ethernet since the weekend(it seems to not receive any packet). I did not
look after it because have other patches on my todo list currently. Maybe
it is the same error?
Greetings,
Hannes
next prev parent reply other threads:[~2013-08-06 21:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 13:51 linux-next: Tree for Aug 6 [ wireless | iwlwifi | mac80211 ? ] Sedat Dilek
2013-08-06 13:54 ` Johannes Berg
2013-08-06 14:02 ` Sedat Dilek
2013-08-06 14:46 ` Sedat Dilek
2013-08-06 14:50 ` Johannes Berg
2013-08-06 14:56 ` Sedat Dilek
2013-08-06 14:57 ` Johannes Berg
2013-08-06 14:59 ` Sedat Dilek
2013-08-06 15:09 ` Sedat Dilek
2013-08-06 15:18 ` Johannes Berg
2013-08-06 15:20 ` Sedat Dilek
2013-08-06 15:27 ` Sedat Dilek
2013-08-06 15:29 ` Johannes Berg
2013-08-06 15:43 ` Sedat Dilek
2013-08-06 15:58 ` Sedat Dilek
2013-08-06 16:03 ` Johannes Berg
2013-08-06 16:07 ` Sedat Dilek
2013-08-06 16:51 ` Sedat Dilek
2013-08-06 18:26 ` Sedat Dilek
2013-08-06 18:35 ` Sedat Dilek
2013-08-06 19:08 ` Johannes Berg
2013-08-06 19:14 ` Sedat Dilek
2013-08-06 19:18 ` Johannes Berg
2013-08-06 19:32 ` Sedat Dilek
2013-08-06 19:47 ` Sedat Dilek
2013-08-06 21:29 ` Phil Sutter
2013-08-06 21:40 ` Sedat Dilek
2013-08-06 21:45 ` Johannes Berg
2013-08-06 21:56 ` Hannes Frederic Sowa [this message]
2013-08-06 22:55 ` Sedat Dilek
2013-08-06 23:07 ` Hannes Frederic Sowa
2013-08-06 23:14 ` Sedat Dilek
2013-08-06 21:58 ` Johannes Berg
2013-08-08 21:13 ` Phil Sutter
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=20130806215657.GA16410@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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