netdev - Re: [PATCH v3 2/2] gianfar: Fix invalid TX frames returned on error queue when time stamping

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20120112.152619.2007546642181896584.davem@davemloft.net>
Date:	Thu, 12 Jan 2012 15:26:19 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	manfred.rudigier@...cron.at
Cc:	netdev@...r.kernel.org, afleming@...escale.com,
	avorontsov@...sta.com, richardcochran@...il.com,
	eric.dumazet@...il.com
Subject: Re: [PATCH v3 2/2] gianfar: Fix invalid TX frames returned on
 error queue when time stamping

From: Manfred Rudigier <manfred.rudigier@...cron.at>
Date: Tue, 10 Jan 2012 10:26:51 +0100

> When TX time stamping for PTP messages is enabled on a socket, a time
> stamp is returned on the socket error queue to the user space application
> after the frame was transmitted. The transmitted frame is also returned on
> the error queue so that an application knows to which frame the time stamp
> belongs.
> 
> In the current implementation the TxFCB is immediately followed by the
> frame. Since the eTSEC inserts the TX time stamp 8 bytes after the TxFCB,
> parts of the frame have been overwritten and an invalid frame was returned
> on the socket error queue.
> 
> This patch fixes the described problem by adding additional 16 padding
> bytes between the TxFCB and the frame for all messages sent from a time
> stamping enabled socket (other sockets are not affected).
> 
> Signed-off-by: Manfred Rudigier <manfred.rudigier@...cron.at>

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