From: Patrick McHardy <kaber@trash.net>
To: Arnaud Ebalard <arno@natisbad.org>
Cc: netdev@vger.kernel.org,
Debian Kernel Team <debian-kernel@lists.debian.org>,
Silviu Vlasceanu <silviuvlasceanu@yahoo.com>
Subject: Re: [BUG,NETFILTER] nfqnl_mangle() not requesting enough space for bigger reinjected packet.
Date: Tue, 06 May 2008 12:20:32 +0200 [thread overview]
Message-ID: <482030F0.5010907@trash.net> (raw)
In-Reply-To: <87skx44lfw.fsf@natisbad.org>
Arnaud Ebalard wrote:
> Hi,
>
> Sorry for the latency.
>
Same here :)
> I think I just found why the 2.6.24 *Debian* kernel undergo the same
> issue. Basically because 2.6.24.4 kernel are also affected. Debian
> maintainers do apply during the build the patch switching to the use of
> skb_copy_expand() instead of pskb_expand_head() (as part of 2.6.24.4
> patch) ;-) :
>
> $:/tmp/linux-2.6-2.6.24/debian/patches$ grep -R _expand .
> ./features/all/vserver/vs2.2.0-rc5.patch:@@ -2098,6 +2107,8 @@ int may_expand_vm(struct mm_struct *mm,
> ./features/all/vserver/vs2.2.0-rc5.patch: if (!may_expand_vm(mm, (new_len - old_len) >> PAGE_SHIFT)) {
> ./bugfix/all/stable/2.6.24.3.patch: static inline int audit_expand(struct audit_buffer *ab, int extra)
> ./bugfix/all/stable/2.6.24.3.patch:- int ret = pskb_expand_head(skb, skb_headroom(skb), extra,
> ./bugfix/all/stable/2.6.24.3.patch:+ int ret = pskb_expand_head(skb, 0, extra, ab->gfp_mask);
> ./bugfix/all/stable/2.6.24.3.patch: audit_log_lost("out of memory in audit_expand");
> ./bugfix/all/stable/2.6.24.4.patch:@@ -1699,6 +1699,11 @@ mptsas_sas_expander_pg0(MPT_ADAPTER *ioc, struct mptsas_portinfo *port_info,
> ./bugfix/all/stable/2.6.24.4.patch:- err = pskb_expand_head(e->skb, 0,
> ./bugfix/all/stable/2.6.24.4.patch:+ nskb = skb_copy_expand(e->skb, 0,
> ./bugfix/all/stable/2.6.24.4.patch:- err = pskb_expand_head(e->skb, 0,
> ./bugfix/all/stable/2.6.24.4.patch:+ nskb = skb_copy_expand(e->skb, 0,
> ./bugfix/all/stable/2.6.24.4.patch:- err = pskb_expand_head(e->skb, 0,
> ./bugfix/all/stable/2.6.24.4.patch:+ nskb = skb_copy_expand(e->skb, 0,
>
>
> I do not know precisely the process but I added the Debian Kernel
> Team in Cc, so that they are aware of the issue, with a pointer to the
> beginning of the thread:
>
> Archived-At: <http://permalink.gmane.org/gmane.linux.network/92426>
>
> >From my understanding, I think that the Debian version of the 2.6.24 on
> which I initially made my tests on was ok (pre-2.6.24.4). Then, I
> updated it to a new 2.6.24-1 Debian version (so did Silviu), which
> introduced the bug (it is in fact 2.6.24.4-based).
>
> To sum it up, all post 2.6.24.4 kernels need the patch (2.6.24.4
> included). This includes all 2.6.25.
Thanks for the explanation. I'll send it to -stable after running some
tests.
next prev parent reply other threads:[~2008-05-06 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 17:31 [BUG,NETFILTER] nfqnl_mangle() not requesting enough space for bigger reinjected packet Arnaud Ebalard
2008-05-06 10:20 ` Patrick McHardy [this message]
2008-05-13 7:28 ` Arnaud Ebalard
2008-05-13 11:45 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2008-04-26 17:24 Arnaud Ebalard
2008-04-29 14:07 ` Silviu Vlasceanu
2008-04-29 14:14 ` 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=482030F0.5010907@trash.net \
--to=kaber@trash.net \
--cc=arno@natisbad.org \
--cc=debian-kernel@lists.debian.org \
--cc=netdev@vger.kernel.org \
--cc=silviuvlasceanu@yahoo.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).