From: Florian Westphal <fw@strlen.de>
To: Jacob Rasmussen <jacobraz@chromium.org>
Cc: mkubecek@suse.cz, fw@strlen.de, netfilter-devel@vger.kernel.org,
pablo@netfilter.org
Subject: Re: userspace conntrack helper and confirming the master conntrack
Date: Fri, 15 May 2020 16:36:32 +0200 [thread overview]
Message-ID: <20200515143632.GF11406@breakpoint.cc> (raw)
In-Reply-To: <20200513175408.195863-1-jacobraz@google.com>
Jacob Rasmussen <jacobraz@chromium.org> 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.
next prev parent reply other threads:[~2020-05-15 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 8:49 userspace conntrack helper and confirming the master conntrack Michal Kubecek
2019-07-18 9:21 ` Florian Westphal
2019-07-18 10:18 ` Michal Kubecek
2019-07-19 16:47 ` Pablo Neira Ayuso
2019-09-04 12:16 ` Michal Kubecek
2019-09-10 23:24 ` Pablo Neira Ayuso
2019-09-11 8:17 ` Michal Kubecek
2020-05-13 17:54 ` Jacob Rasmussen
2020-05-15 14:36 ` Florian Westphal [this message]
2020-05-15 14:37 ` [PATCH nf] netfilter: make conntrack userspace helpers work again Florian Westphal
2020-05-15 15:17 ` userspace conntrack helper and confirming the master conntrack Michal Kubecek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200515143632.GF11406@breakpoint.cc \
--to=fw@strlen.de \
--cc=jacobraz@chromium.org \
--cc=mkubecek@suse.cz \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).