[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170623.143846.888437777181372282.davem@davemloft.net>
Date: Fri, 23 Jun 2017 14:38:46 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: richardcochran@...il.com
Cc: netdev@...r.kernel.org, Manfred.Rudigier@...cron.at,
stefan.sorensen@...ctralink.com
Subject: Re: [PATCH net] net: dp83640: Avoid NULL pointer dereference.
From: Richard Cochran <richardcochran@...il.com>
Date: Fri, 23 Jun 2017 17:51:31 +0200
> The function, skb_complete_tx_timestamp(), used to allow passing in a
> NULL pointer for the time stamps, but that was changed in commit
> 62bccb8cdb69051b95a55ab0c489e3cab261c8ef ("net-timestamp: Make the
> clone operation stand-alone from phy timestamping"), and the existing
> call sites, all of which are in the dp83640 driver, were fixed up.
>
> Even though the kernel-doc was subsequently updated in commit
> 7a76a021cd5a292be875fbc616daf03eab1e6996 ("net-timestamp: Update
> skb_complete_tx_timestamp comment"), still a bug fix from Manfred
> Rudigier came into the driver using the old semantics. Probably
> Manfred derived that patch from an older kernel version.
>
> This fix should be applied to the stable trees as well.
>
> Fixes: 81e8f2e930fe ("net: dp83640: Fix tx timestamp overflow handling.")
> Signed-off-by: Richard Cochran <richardcochran@...il.com>
Applied and queued up for -stable, thank you.
Powered by blists - more mailing lists