From: sinter <sinter.salt@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: BUG in 2.6.29 final: broken network connection
Date: Tue, 24 Mar 2009 18:12:14 +0100 [thread overview]
Message-ID: <200903241812.14577.sinter.salt@gmx.de> (raw)
Hi everybody,
ftp, ping, IP forwarding, IP masquerading etc., in short: everything having to
do with networking is broken using kernel 2.6.29.
My thousand thanks for that again go to Mr. David S. Miller, kernel
contributor of the netdev section, who again and again is adding his SOB under
untested crap code that itself breaks networking hardware by reaching the
kernel mainline via git patches.
In the past exactly that happened again and again, and it is particularly Mr.
David S. Miller himself who, proven by facts, is not willing to learn to stay
away from sending in malicious code via the git path.
I am really wondering why Linus Torvalds is still trusting him, as it is a
fact that not everybody can send in code just like that, i. e. without
restrictions.
It cost me almost 1 complete day (and again I do state that this is not the
first time that some unqualified hacker operating with the responsibility of Mr.
David S. Miller deeply sucks and steals my nerves and wastes my time) to find
out that the following patch needs to be reverted to make networking services
in 2.6.29 final available again for everybody.
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -2588,9 +2588,9 @@ static int process_backlog(struct napi_struct *napi, int
quota)
local_irq_disable();
skb = __skb_dequeue(&queue->input_pkt_queue);
if (!skb) {
- __napi_complete(napi);
local_irq_enable();
- break;
+ napi_complete(napi);
+ goto out;
}
local_irq_enable();
@@ -2599,6 +2599,7 @@ static int process_backlog(struct napi_struct *napi, int
quota)
napi_gro_flush(napi);
+out:
return work;
}
@@ -2671,7 +2672,7 @@ void netif_napi_del(struct napi_struct *napi)
struct sk_buff *skb, *next;
list_del_init(&napi->dev_list);
- kfree(napi->skb);
+ kfree_skb(napi->skb);
for (skb = napi->gro_list; skb; skb = next) {
next = skb->next;
Best wishes
Uwe
next reply other threads:[~2009-03-24 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 17:12 sinter [this message]
2009-03-24 17:25 ` BUG in 2.6.29 final: broken network connection Alan Cox
2009-03-24 17:40 ` Eric Dumazet
2009-03-24 18:18 ` sinter
2009-03-24 19:42 ` David Miller
2009-03-24 19:42 ` Ingo Molnar
[not found] ` <200903242149.59640.sinter.salt@gmx.de>
2009-03-24 21:45 ` Ingo Molnar
[not found] <cjisi-2Kz-11@gated-at.bofh.it>
[not found] ` <cjiC5-2XR-15@gated-at.bofh.it>
[not found] ` <cjiVm-3mJ-23@gated-at.bofh.it>
2009-03-24 18:40 ` Niel Lambrechts
2009-03-25 12:30 ` markus reichelt
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=200903241812.14577.sinter.salt@gmx.de \
--to=sinter.salt@gmx.de \
--cc=linux-kernel@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