From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
syzbot+c7aabc9fe93e7f3637ba@syzkaller.appspotmail.com
Subject: Re: [PATCH nf-next] netfilter: ecache: don't look for ecache extension on dying/unconfirmed conntracks
Date: Sat, 26 Oct 2019 20:27:39 +0200 [thread overview]
Message-ID: <20191026182739.GA3321@breakpoint.cc> (raw)
In-Reply-To: <20191026103607.urwwmxpwrxdcwijm@salvia>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > I plan to send a patch for nf tree to alter nf_conntrack_confirm()
> > to not cache the ct -- I think its a bug too, we should call
> > nf_ct_deliver_cached_events() on the ct that is assigned to skb *now*,
> > not the old one.
>
> This is the clash resolution that is triggering this path you describe
> in this note.
Yes, its the clash resolution.
prev parent reply other threads:[~2019-10-26 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 16:56 [PATCH nf-next] netfilter: ecache: don't look for ecache extension on dying/unconfirmed conntracks Florian Westphal
2019-10-26 10:36 ` Pablo Neira Ayuso
2019-10-26 18:27 ` Florian Westphal [this message]
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=20191026182739.GA3321@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzbot+c7aabc9fe93e7f3637ba@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).