netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pierre Chifflier <chifflier@edenwall.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: WIP/RFC: add new module ebt_NFQUEUE for ebtables
Date: Fri, 04 Feb 2011 14:20:19 +0100	[thread overview]
Message-ID: <4D4BFD13.8090306@edenwall.com> (raw)
In-Reply-To: <4D4BFA1D.4070007@trash.net>

On 02/04/2011 02:07 PM, Patrick McHardy wrote:
> On 04.02.2011 11:05, Pierre Chifflier wrote:
>> On 02/03/2011 03:32 PM, Pierre Chifflier wrote:
>>
>>> The current problems I'm facing are described in the previous mail,
>>> and specifically a fault in skb_free, deep inside the br_handle_frame code
>>> after a reinject.
>>> I'll try to isolate a backtrace when it happens.
>>>
>>
>> Hi,
>>
>> The backtrace is more or less the same as the one in Jan's email
>> <alpine.LNX.2.01.1102031605330.21536@obet.zrqbmnf.qr>
>> (Kernel crash with repeated NF invocation)
>>
>> At the moment, I'm wondering if I'm not having several cumulated
>> problems, which may be triggered more easily by my modifications ...
> 
> We can't really help debug this without seeing the code, so please
> post your current version (either privately or to the list).

Hi Patrick,

I just realized I didn't cc: you when sending the patches, but I send
them yesterday on the list (in reply to this thread)

<1296743540-8148-2-git-send-email-chifflier@edenwall.com>
[PATCH 1/3] Make the afinfo structure optional in nf_queue and nf_reinject

And the 2 following.
Sorry for the missing cc.

Pierre

  reply	other threads:[~2011-02-04 13:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 20:55 ebtables_nfqueue: missing structure afinfo Pierre Chifflier
2011-01-25 10:34 ` Patrick McHardy
2011-02-02 19:22   ` Pierre Chifflier
2011-02-02 22:59     ` Patrick McHardy
2011-02-03 14:32       ` WIP/RFC: add new module ebt_NFQUEUE for ebtables Pierre Chifflier
2011-02-03 20:19         ` Bart De Schuymer
2011-02-04 10:05         ` Pierre Chifflier
2011-02-04 13:07           ` Patrick McHardy
2011-02-04 13:20             ` Pierre Chifflier [this message]
2011-02-04 13:21               ` Patrick McHardy
2011-02-03 14:32       ` [PATCH 1/3] Make the afinfo structure optional in nf_queue and nf_reinject Pierre Chifflier
2011-02-04 13:27         ` Patrick McHardy
2011-02-04 14:15           ` Pierre Chifflier
2011-02-03 14:32       ` [PATCH 2/3] bridge: add support for the EBT_QUEUE target Pierre Chifflier
2011-02-03 14:32       ` [PATCH 3/3] bridge: add new target NFQUEUE for ebtables Pierre Chifflier
2011-02-04 13:25         ` Patrick McHardy
2011-02-04 13:40           ` Pierre Chifflier
2011-02-04 13:41             ` Patrick McHardy
     [not found]               ` <4D5104C4.3010105@edenwall.com>
     [not found]                 ` <4D59C047.5050404@trash.net>
2011-02-16 16:57                   ` [RFH] " Pierre Chifflier
2011-02-17 10:47                     ` Patrick McHardy
2011-02-17 13:37                       ` Pierre Chifflier
2011-02-18 13:42                         ` Patrick McHardy

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=4D4BFD13.8090306@edenwall.com \
    --to=chifflier@edenwall.com \
    --cc=kaber@trash.net \
    --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).