All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Miller <davem@davemloft.net>
Cc: francois.valenduc@tvcablenet.be, akpm@linux-foundation.org,
	bugme-daemon@bugzilla.kernel.org, linux-wireless@vger.kernel.org,
	linville@tuxdriver.com, netdev@vger.kernel.org,
	jussi.kivilinna@mbnet.fi
Subject: Re: [Bugme-new] [Bug 11144] New: dhcp doesn't work with iwl4965
Date: Thu, 24 Jul 2008 10:58:57 +0200	[thread overview]
Message-ID: <48884451.1090703@trash.net> (raw)
In-Reply-To: <20080723.142147.61941255.davem@davemloft.net>

David Miller wrote:
> From: Patrick McHardy <kaber@trash.net>
> Date: Wed, 23 Jul 2008 18:25:48 +0200
> 
>> We can't fit them into the cb together, I don't see a way to
>> shrink ieee80211_tx_info.
>>
>> Maybe one of the wireless folks can suggest something? Is it
>> really necessary to pass the full struct ieee80211_tx_info
>> through the qdisc layer, or could the struct be split? It
>> needs to find a way to co-exist peacefully with qdiscs'
>> skb->cb usage.
> 
> This is another area that got mangled up in the ->select_queue()
> conversion of the WME bits, but in another aspect this problem
> existed beforehand as well.
> 
> Specifically, when RX packets get requeued out to transmit in
> the code in net/mac80211/rx.c that resends packets back out the
> wireless device by setting a bit in the SKB CB then calling
> dev_queue_xmit().
> 
> That's completely illegal :-)

It seems its doing even more illegal things that were also
present previously. The ieee80211_master_start_xmit function
expects to get a valid IEEE80211_SKB_CB, which means it
expects it to survive through the entire qdisc layer. I'm
not sure how packets get to the master device from the
subifs though, so I might be wrong.



WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: francois.valenduc-bmtTS95sd5BUM80lpFwj4w@public.gmane.org,
	akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
	bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	jussi.kivilinna-E01nCVcF24I@public.gmane.org
Subject: Re: [Bugme-new] [Bug 11144] New: dhcp doesn't work with iwl4965
Date: Thu, 24 Jul 2008 10:58:57 +0200	[thread overview]
Message-ID: <48884451.1090703@trash.net> (raw)
In-Reply-To: <20080723.142147.61941255.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>

David Miller wrote:
> From: Patrick McHardy <kaber-dcUjhNyLwpNeoWH0uzbU5w@public.gmane.org>
> Date: Wed, 23 Jul 2008 18:25:48 +0200
> 
>> We can't fit them into the cb together, I don't see a way to
>> shrink ieee80211_tx_info.
>>
>> Maybe one of the wireless folks can suggest something? Is it
>> really necessary to pass the full struct ieee80211_tx_info
>> through the qdisc layer, or could the struct be split? It
>> needs to find a way to co-exist peacefully with qdiscs'
>> skb->cb usage.
> 
> This is another area that got mangled up in the ->select_queue()
> conversion of the WME bits, but in another aspect this problem
> existed beforehand as well.
> 
> Specifically, when RX packets get requeued out to transmit in
> the code in net/mac80211/rx.c that resends packets back out the
> wireless device by setting a bit in the SKB CB then calling
> dev_queue_xmit().
> 
> That's completely illegal :-)

It seems its doing even more illegal things that were also
present previously. The ieee80211_master_start_xmit function
expects to get a valid IEEE80211_SKB_CB, which means it
expects it to survive through the entire qdisc layer. I'm
not sure how packets get to the master device from the
subifs though, so I might be wrong.


--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-07-24  8:59 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11144-10286@http.bugzilla.kernel.org/>
2008-07-22 10:48 ` [Bugme-new] [Bug 11144] New: dhcp doesn't work with iwl4965 Andrew Morton
2008-07-22 10:52   ` Patrick McHardy
2008-07-23  7:58   ` François Valenduc
2008-07-23  7:58     ` François Valenduc
2008-07-23  7:59     ` François Valenduc
2008-07-23  8:05     ` Andrew Morton
2008-07-23  8:05       ` Andrew Morton
2008-07-23  9:17       ` François Valenduc
2008-07-23  9:17         ` François Valenduc
2008-07-23 10:12         ` Patrick McHardy
2008-07-23 10:12           ` Patrick McHardy
2008-07-23 11:29           ` François Valenduc
2008-07-23 11:29             ` François Valenduc
2008-07-23 11:31             ` Patrick McHardy
2008-07-23 11:31               ` Patrick McHardy
2008-07-23 11:58               ` François Valenduc
2008-07-23 12:36               ` François Valenduc
2008-07-23 12:36                 ` François Valenduc
2008-07-23 12:44                 ` Patrick McHardy
2008-07-23 12:44                   ` Patrick McHardy
2008-07-23 12:51                   ` Patrick McHardy
2008-07-23 12:51                     ` Patrick McHardy
2008-07-23 14:57                     ` François Valenduc
2008-07-23 14:57                       ` François Valenduc
2008-07-23 15:18                       ` Patrick McHardy
2008-07-23 15:19                         ` Patrick McHardy
2008-07-23 15:42                           ` François Valenduc
2008-07-23 15:42                             ` François Valenduc
2008-07-23 15:52                             ` Patrick McHardy
2008-07-23 15:52                               ` Patrick McHardy
2008-07-23 15:58                               ` François Valenduc
2008-07-23 15:58                                 ` François Valenduc
2008-07-23 15:59                                 ` Patrick McHardy
2008-07-23 15:59                                   ` Patrick McHardy
2008-07-23 16:25                                   ` Patrick McHardy
2008-07-23 16:25                                     ` Patrick McHardy
2008-07-23 21:21                                     ` David Miller
2008-07-24  8:58                                       ` Patrick McHardy [this message]
2008-07-24  8:58                                         ` Patrick McHardy
2008-07-24 10:17                                         ` Tomas Winkler
2008-07-24 10:17                                           ` Tomas Winkler
2008-07-24 10:19                                           ` Patrick McHardy
2008-07-24 10:19                                             ` Patrick McHardy
2008-07-24 11:35                                             ` Tomas Winkler
2008-07-24 11:35                                               ` Tomas Winkler
2008-07-24 11:45                                               ` Johannes Berg
2008-07-24 11:45                                                 ` Johannes Berg
2008-07-30 18:04                                                 ` François Valenduc
2008-07-30 18:04                                                   ` François Valenduc

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=48884451.1090703@trash.net \
    --to=kaber@trash.net \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=davem@davemloft.net \
    --cc=francois.valenduc@tvcablenet.be \
    --cc=jussi.kivilinna@mbnet.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@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 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.