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: <1324550811.2153.3.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC>
Date:	Thu, 22 Dec 2011 11:46:51 +0100
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Michael Wang <wangyun@...ux.vnet.ibm.com>
Cc:	monstr@...str.eu, David Miller <davem@...emloft.net>,
	John Williams <john.williams@...alogix.com>,
	netdev@...r.kernel.org
Subject: Re: ICMP packets - ll_temac with Microblaze

Le jeudi 22 décembre 2011 à 18:32 +0800, Michael Wang a écrit :
> On 12/21/2011 06:11 PM, Michal Simek wrote:
> 
> > 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.
> > 
> 
> Hi, Michal
> 
> What's the type of icmp you are using? such as "EchoReps", we can find
> the actually handler routine by this type.
> 
> And you said the packet already received by driver, can you tell me the
> way you used to confirm this?
> 
> And have you checked when was the icmp packet being dropped, is it in
> icmp_rcv or before or later?

Packet was dropped right before being queued in RAW socket
receive_queue, because of low sk_rcvbuf setting (against skb->truesize)



--
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