On Thu, Dec 14, 2017 at 12:05 PM, Ed Swierk wrote:
> On Wed, Dec 13, 2017 at 4:58 PM, Pravin Shelar wrote:
>> On Tue, Dec 12, 2017 at 8:17 AM, Ed Swierk
>> wrote:
>>> A short IPv4 packet may have up to 6 bytes of padding following the IP
>>> payload when received on an Ethernet device.
>>>
>>>
On Wed, Dec 13, 2017 at 4:58 PM, Pravin Shelar wrote:
> On Tue, Dec 12, 2017 at 8:17 AM, Ed Swierk wrote:
>> A short IPv4 packet may have up to 6 bytes of padding following the IP
>> payload when received on an Ethernet device.
>>
>> In the normal IPv4 receive path, ip_rcv() trims the packet to
>
On Tue, Dec 12, 2017 at 8:17 AM, Ed Swierk wrote:
> A short IPv4 packet may have up to 6 bytes of padding following the IP
> payload when received on an Ethernet device.
>
> In the normal IPv4 receive path, ip_rcv() trims the packet to
> ip_hdr->tot_len before invoking NF_INET_PRE_ROUTING hooks (i
A short IPv4 packet may have up to 6 bytes of padding following the IP
payload when received on an Ethernet device.
In the normal IPv4 receive path, ip_rcv() trims the packet to
ip_hdr->tot_len before invoking NF_INET_PRE_ROUTING hooks (including
conntrack). Then any subsequent L3+ processing step
