netdev - Re: ICMP packets - ll_temac with Microblaze

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1324463452.2728.21.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
Date:	Wed, 21 Dec 2011 11:30:52 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	monstr@...str.eu
Cc:	David Miller <davem@...emloft.net>,
	John Williams <john.williams@...alogix.com>,
	netdev@...r.kernel.org
Subject: Re: ICMP packets - ll_temac with Microblaze

Le mercredi 21 décembre 2011 à 11:28 +0100, Eric Dumazet a écrit :
> Le mercredi 21 décembre 2011 à 11:11 +0100, Michal Simek a écrit :
> > Hi Eric and David,
> > 
> > I have found one problem with ll_temac driver and
> > this commit: net: more accurate skb truesize
> > sha1: 87fb4b7b533073eeeaed0b6bf7c2328995f6c075
> > 
> > The problem is only with icmp packets from the target. It is sent and driver receive it
> > but it is not proceed to the application.
> > 
> > The problem I see is that kmalloc_node_track_caller allocate
> > specific size and then this size is changed by SKB_WITH_OVERHEAD(ksize(data)).
> > The problem is with netdev_alloc_skb_ip_align which calls __alloc_skb function.
> > 
> > Currently driver uses setting for jumbo frames (9k). When I change it to use mtu (1,5k) then
> > everything is ok.
> > 
> > Can you give me some hints what can be wrong?
> > 
> 
> Is it with SLUB, SLAB or SLOB allocator ?
> 
> 

(I am referring to commit bc417e30f8d
(net: Add back alignment for size for __alloc_skb)



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