[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a53362a9afee4995919c117016209701@intel.com>
Date: Tue, 8 Oct 2019 16:54:04 +0000
From: "Bowers, AndrewX" <andrewx.bowers@...el.com>
To: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [Intel-wired-lan] [PATCH 1/1] ixgbe: protect TX timestamping from
API misuse
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces@...osl.org] On
> Behalf Of Manjunath Patil
> Sent: Saturday, October 5, 2019 8:20 AM
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@...el.com>; davem@...emloft.net;
> intel-wired-lan@...ts.osuosl.org; netdev@...r.kernel.org; linux-
> kernel@...r.kernel.org
> Cc: manjunath.b.patil@...cle.com; christophe.jaillet@...adoo.fr;
> cspradlin@...gle.com
> Subject: [Intel-wired-lan] [PATCH 1/1] ixgbe: protect TX timestamping from
> API misuse
>
> HW timestamping can only be requested for a packet if the NIC is first setup
> via ioctl(SIOCSHWTSTAMP). If this step was skipped, then the ixgbe driver
> still allowed TX packets to request HW timestamping. In this situation, we see
> 'clearing Tx Timestamp hang' noise in the log.
>
> Fix this by checking that the NIC is configured for HW TX timestamping before
> accepting a HW TX timestamping request.
>
> similar-to:
> (26bd4e2 igb: protect TX timestamping from API misuse)
> (0a6f2f0 igb: Fix a test with HWTSTAMP_TX_ON)
>
> Signed-off-by: Manjunath Patil <manjunath.b.patil@...cle.com>
> ---
> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@...el.com>
Powered by blists - more mailing lists