On 8 Aug 2016 7:33 p.m., "Amit Pundir" <amit.pundir@linaro.org> wrote:
>
> Hi Tixy,
>
> On 8 August 2016 at 19:22, Amit Pundir <amit.pundir@linaro.org> wrote:
> > On 2 August 2016 at 21:49, Jon Medhurst (Tixy) <tixy@linaro.org> wrote:
> >> Hi All
> >>
> >> After updating my Juno tree to the 16.07 release of LSK 3.18 I am not
> >> able to boot Android. I narrowed down the problem to the new iptable
> >> validity checks that came in with Linux 3.18.37. If I revert a bunch of
> >> these then things work again, i.e.
> >>
> >> git revert 674c7e173d01~..6a9f9d4e6c5d
> >>
> >> If I don't revert 674c7e173d01 then things remain broken, but it's not
> >> as simple as just that one commit being wrong, because if I only revert
> >> that one by itself it doesn't fix things.
> >
> > Just an FYI that I stumbled upon this upstream commit f4dc77713f80
> > ("netfilter: x_tables: speed up jump target validation") which, from
> > the description, seem to address the same regression which we are
> > facing on lsk-android-4.4. But I have not verified it yet and will
> > keep you posted.
> >
>
> I can confirm that this upstream fix works for me. Verified on
> qemu-system-arm with lsk-v3.18-android snapshot for lts-v3.18.37
> (sorry for reporting it as v4.4 in previous email), as well as your
> "iptables-problem" tree.

Good work diagnosing! Does this apply to the base LTS or is this an interaction with Android patches? Either way it seems we should push it to an upstream, Greg or Google.

>
> Regards,
> Amit Pundir