netdev - Re: [PATCH] Re: PACKET_TX_RING: packet size is too long

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: <20091013.005438.32630424.davem@davemloft.net>
Date:	Tue, 13 Oct 2009 00:54:38 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	gombasg@...aki.hu
Cc:	netdev@...r.kernel.org, johann.baudy@...-log.net
Subject: Re: [PATCH] Re: PACKET_TX_RING: packet size is too long

From: Gabor Gombas <gombasg@...aki.hu>
Date: Sat, 10 Oct 2009 00:05:46 +0200

> Hi,
> 
> Digging list archives I suspect the current value of size_max is the
> remnant of the zero-copy mode that was not merged. So I propose the
> following patch that IMHO makes the value of size_max consistent with
> how the frame is actually handled in tpacket_fill_skb().
> 
> If the zero-copy mode is ever to be resurrected, then the user should
> explicitely request it, and either the length of the extra padding
> should be the same for 32-bit and 64-bit kernels or there must be a way
> to query the value at run time.

Johann, please take a look at this.

Gabor, please resubmit your patch with a proper Signed-off-by:
tag so I can apply it if it is correct.

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