From: 高峰 <fgao@48lvckh6395k16k5.yundunddos.com>
To: "'Jiri Slaby'" <jslaby@suse.cz>,
"'Pablo Neira Ayuso'" <pablo@netfilter.org>
Cc: <kadlec@blackhole.kfki.hu>, "'Florian Westphal'" <fw@strlen.de>,
<netfilter-devel@vger.kernel.org>, <coreteam@netfilter.org>,
"'Linux kernel mailing list'" <linux-kernel@vger.kernel.org>
Subject: RE: 4.12 nf_conntrack_expect crash
Date: Tue, 18 Jul 2017 08:23:26 +0800 [thread overview]
Message-ID: <000301d2ff5c$135cab00$3a160100$@ikuai8.com> (raw)
In-Reply-To: <12e1fdf4-2936-d2a7-e537-1038fbf5b7a3@suse.cz>
Hi Jiri,
> From: Jiri Slaby [mailto:jslaby@suse.cz]
> Subject: Re: 4.12 nf_conntrack_expect crash
>
> On 07/17/2017, 04:49 PM, Jiri Slaby wrote:
> > Hi,
> >
> > on my system, I see a crash in del_timer invoked in nf_conntrack_expect.
> > See the attached picture.
> >
> > I somehow suspect this commit:
> >
> > commit ec0e3f01114ad327112432a4da8840eb22fed577
> > Author: Gao Feng <fgao@ikuai8.com>
> > Date: Mon Mar 27 10:31:26 2017 +0800
> >
> > netfilter: nf_ct_expect: Add nf_ct_remove_expect()
> >
> >
> > I am going to play with it (debug, try to revert, etc.) if you have no
> > better idea...
>
> This?
>
> --- a/net/netfilter/nf_conntrack_expect.c
> +++ b/net/netfilter/nf_conntrack_expect.c
> @@ -422,7 +422,7 @@ static inline int __nf_ct_expect_check(struct
> nf_conntrack_expect *expect)
> h = nf_ct_expect_dst_hash(net, &expect->tuple);
> hlist_for_each_entry_safe(i, next, &nf_ct_expect_hash[h], hnode) {
> if (expect_matches(i, expect)) {
> - if (nf_ct_remove_expect(expect))
> + if (nf_ct_remove_expect(i))
> break;
> } else if (expect_clash(i, expect)) {
> ret = -EBUSY;
>
>
>
> >
> > thanks,
> >
>
>
> --
> js
> suse labs
It is a bug caused by typo indeed. I am sorry about that.
And Florian has fixed it recently, but thanks your catch again.
Regards
Feng
prev parent reply other threads:[~2017-07-18 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 14:49 Jiri Slaby
2017-07-17 14:54 ` Jiri Slaby
2017-07-18 0:23 ` 高峰 [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='000301d2ff5c$135cab00$3a160100$@ikuai8.com' \
--to=fgao@48lvckh6395k16k5.yundunddos.com \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=jslaby@suse.cz \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome