From: Patrick McHardy <kaber@trash.net>
To: Dong Wei <dwei.zh@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Port back 2.6 kernel patch to 2.4 which fixed bridge module panic when received special fragments
Date: Wed, 13 Jan 2010 10:44:57 +0100 [thread overview]
Message-ID: <4B4D9619.1010803@trash.net> (raw)
In-Reply-To: <3104bfb61001130142p5011c1cj6b01bf80ea9aee21@mail.gmail.com>
Dong Wei wrote:
> Hi, Patrick
>
> Thanks for your reply.
>
> I checked the ebtables website, but the mail-list just point to the
> netfilter mail list.
>
> So, would you please tell me who should I send this mail to ?
Try Bart De Schuymer <bdschuym@pandora.be>.
>
> 2010/1/13 Patrick McHardy <kaber@trash.net>:
>> Dong Wei wrote:
>>> Hi, All
>>>
>>> linux-2.6.32.3 fixed a kernel panic problem in bridge module when
>>> received special fragments.
>>>
>>> see: http://git.kernel.org/?p=linux/kernel/git/hpa/linux-2.6-allstable.git;a=commit;h=8fa9ff6849bb86c59cc2ea9faadf3cb2d5223497
>>>
>>> There is a ebtables kernel patch ebtables-brnf-11-2_vs_2.4.31.diff.gz
>>> which port back bridge netfilter. After applied the kernel patch, the
>>> kernel panic problem will be introduced to the kernel. I made a kernel
>>> patch on 2.4.37.7 which can fix this problem. I think this patch
>>> should be merged to the ebtables-brnf-11-2_vs_2.4.31.diff.gz .
>> You need to send this to whomever is maintaining that patch,
>> probably Bart.
>>
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-01-13 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 9:30 Port back 2.6 kernel patch to 2.4 which fixed bridge module panic when received special fragments Dong Wei
2010-01-13 9:33 ` Patrick McHardy
2010-01-13 9:42 ` Dong Wei
2010-01-13 9:44 ` Patrick McHardy [this message]
2010-01-13 19:44 ` Bart De Schuymer
2010-01-14 8:46 ` 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=4B4D9619.1010803@trash.net \
--to=kaber@trash.net \
--cc=dwei.zh@gmail.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).