netdev - Re: [PATCH] net: Handle gso packets in dev_forward

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: <m1ei5rghqd.fsf@fess.ebiederm.org>
Date:	Mon, 28 Mar 2011 12:36:26 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	greearb@...delatech.com, arnd@...db.de, kaber@...sh.net,
	Daniel Lezcano <daniel.lezcano@...e.fr>
Subject: Re: [PATCH] net: Handle gso packets in dev_forward_skb

Eric Dumazet <eric.dumazet@...il.com> writes:

> Le dimanche 27 mars 2011 à 18:09 -0700, David Miller a écrit :
>> From: ebiederm@...ssion.com (Eric W. Biederman)
>> Date: Mon, 21 Mar 2011 15:00:56 -0700
>> 
>> > Eric Dumazet <eric.dumazet@...il.com> writes:
>> > 
>> >> Hmm, did you follow http://patchwork.ozlabs.org/patch/86815/
>> >> discussion ?
>> > 
>> > No.  It seems I missed it, but I do have the same problem, and
>> > essentially the same fix. 
>> 
>> Can someone work on getting this straightened out and resubmit the
>> final patch so I can apply something?
>> 
>
> Apparently Daniel is busy.
>
> I guess we can use Eric B. patch, then ?

That sounds good to me.

After reviewing the other thread to the best of my knowledge there are
no issues with the patch I submitted.  At worst I am 4 bytes extra
permissive about the mtu because of the way that path handles vlan
headers and that isn't something my patch changed.

Eric


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