Search Linux Wireless

Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 23.2.2009 16:35, Bob Copeland wrote:
As I understand it, yes, we don't do the right thing when the more flag
is set.  We're supposed to keep processing packets until we get one with
the done flag, and then all of that is supposed to be merged into a single
packet.  Other flags such as the rx rate are only valid on the final
packet.

What I don't understand is how we can proceed further, if we should never get done flag set according to the specs for the buffer which has more flag set. We should hit (unlikely(ret == -EINPROGRESS)) test everytime.

So I am not sure if the jumbo packets are causing bad things to happen,
or if they are an indication that something bad has already happened.

I don't know, it was just an idea. I tried to lower rxbufsize to 1000 and see no problems so far (except unsupported jumbo warnings and packet loss indeed).
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux