From: Patrick McHardy <kaber@trash.net>
To: Juneja Kapil <Kapil.Juneja@freescale.com>
Cc: netfilter-devel@vger.kernel.org,
Medve Emilian <Emilian.Medve@freescale.com>
Subject: Re: [PATCH] nf_conntrack_core: Updated nf_conntrack to destroy/refresh conn irrespective of del_timer status
Date: Fri, 29 Feb 2008 13:23:41 +0100 [thread overview]
Message-ID: <47C7F94D.5020801@trash.net> (raw)
In-Reply-To: <2A6F278C5B66C4459AF4013E77A40CD30122F862@zin33exm20.fsl.freescale.net>
Juneja Kapil wrote:
> Hi Patrick,
>
>> That sounds pretty reasonable. Is that code available somewhere?
>
> We are working on licensing aspects and will be glad to share the code
> as and when we get approval.
>
OK thanks.
>>> Can you describe the race scenario mentioned by you?
>>
>> Very simple:
>>
>> CPU0 CPU1
>> timer goes off
>> refresh_timer: mod_timer, rearm death_by_timeout()
>>
>> timer goes off again
>>
>> Using del_timer prevents us from rearming the timer if it
>> already went off.
>
> Thanks for the explanation. I was probably only thinking of the non-SMP
> scenarios. However, I feel that if this cannot be done this simple way,
> then we are in a bit trouble because our need is to make
> nf_ct_refresh_acct work independent of the existing timer being dead or
> alive.
> While we think about a possible alternatives on respin of patch/control
> module, can you provide some insight into any other alternatives.
The IPS_FIXED_TIMEOUT_BIT should work I guess. It skips
timer updates, but still does accounting (at least in
the current kernel version).
prev parent reply other threads:[~2008-02-29 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 5:19 [PATCH] nf_conntrack_core: Updated nf_conntrack to destroy/refresh conn irrespective of del_timer status Kapil Juneja
2008-02-25 12:11 ` Patrick McHardy
2008-02-26 7:39 ` Juneja Kapil
2008-02-27 13:00 ` Patrick McHardy
2008-02-29 9:26 ` Juneja Kapil
2008-02-29 12:23 ` Patrick McHardy [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=47C7F94D.5020801@trash.net \
--to=kaber@trash.net \
--cc=Emilian.Medve@freescale.com \
--cc=Kapil.Juneja@freescale.com \
--cc=netfilter-devel@vger.kernel.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).