Re: [PATCH 4.4 08/56] ath10k: fix rfc1042 header retrieval in QCA4019 with eth decap mode

[Sriram R]

Hi Ben,

On 2018-06-04 23:22, Ben Hutchings wrote:
> On Mon, 2018-05-14 at 08:48 +0200, Greg Kroah-Hartman wrote:
> > 4.4-stable review patch.ÂÂIf anyone has any objections, please let me 
> > know.
> >
> > ------------------
> >
> > From: Vasanthakumar Thiagarajan <vthiagar@xxxxxxxxxxxxxxxx>
> >
> > commit 2f38c3c01de945234d23dd163e3528ccb413066d upstream.
> >
> > Chipset from QCA99X0 onwards (QCA99X0, QCA9984, QCA4019 & future)
> > rx_hdr_status is not padded to align in 4-byte boundary. Define a
> > new hw_params field to handle different alignment behaviour between
> > different hw. This patch fixes improper retrieval of rfc1042 header
> > with QCA4019. This patch along with "ath10k: Properly remove padding
> > from the start of rx payload" will fix traffic failure in ethernet
> > decap mode for QCA4019.
> >
> > Signed-off-by: Vasanthakumar Thiagarajan <vthiagar@xxxxxxxxxxxxxxxx>
> > Signed-off-by: Kalle Valo <kvalo@xxxxxxxxxxxxxxxx>
> > Signed-off-by: Sriram R <srirrama@xxxxxxxxxxxxxx>
> > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> [...]
>
> I'm curious as to why this backport doesn't include the change to
> ath10k_htt_rx_h_find_rfc1042().  I understand that the addition of the
> new field is a dependency for the following patch, but shouldn't the
> fix included in the upstream commit also be applied to 4.4?
  Our main intention with this patchset [1] was to provide fix for 
replay detection security issue seen in ath10k driver which needed to be 
in the stable releases.

And, as per stable tree guidelines we wanted the patchset to have only 
one and this important fix .

Also we felt the change in ath10k_htt_rx_h_find_rfc1042() is currently 
not  a must-have fix in 4.4 stable tree .

[1]
https://patchwork.kernel.org/patch/10370863/
https://patchwork.kernel.org/patch/10370865/

Thanks and Regards,
Sriram.R

> Ben.