On Fri, May 15, 2020 at 04:36:32PM +0200, Florian Westphal wrote: > Jacob Rasmussen <jacobraz@xxxxxxxxxxxx> wrote: > > I'm encountering a bug on Chrome OS that I believe to be caused by commit 827318feb69cb07ed58bb9b9dd6c2eaa81a116ad and I was wondering if there was any update on a fix/revert landing for this. > > If a fix has already landed would anyone mind pointing me to the specific commit because I haven't been able to find it on my own. > > Right, sorry about this. > Its most definitely caused by 827318feb69cb07ed58bb9b9dd6c2eaa81a116ad. > > Unfortunately I have no easy way to validate the fix. > If you could help speeding this up it would be great if you could test > the candidate fix which I will send in a minute. > > I've checked that it doesn't break conntrack in obvious ways and that > nft_queue.sh self test still passes. Ah, my fault, I completely forgot this. Hopefully I'll be able to test the fix this weekend. Michal
