mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Ebbert <76306.1226@compuserve.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.9 Page Allocation Failures w/TSO+rollup.patch
Date: Mon, 25 Oct 2004 14:53:52 -0400	[thread overview]
Message-ID: <200410251456_MC3-1-8D29-C332@compuserve.com> (raw)

Nicj Piggin wrote:

> Does it cause any noticable problems? If not, then stay with
> 2.6.9.
>
> However, it would be nice to get to the bottom of it. It might
> just be happening by chance on 2.6.9 but not 2.6.8.1 though...

  Isn't this the problem fixed by the below patch?  (Sorry I didn't
get sender name when I collected it.)  Some were skeptical this
would fix it but it has worked for those who tried...

  Oh and BTW what is rollup.patch?


# The following patch makes it allocate skb_headlen(skb) - len instead
# of skb->len - len.  When skb is linear there is no difference.  When
# it's non-linear we only ever copy the bytes in the header.
#
===== net/ipv4/tcp_output.c 1.67 vs edited =====
--- 1.67/net/ipv4/tcp_output.c  2004-10-01 13:56:45 +10:00
+++ edited/net/ipv4/tcp_output.c        2004-10-17 18:58:47 +10:00
@@ -455,8 +455,12 @@
 {
        struct tcp_opt *tp = tcp_sk(sk);
        struct sk_buff *buff;
-       int nsize = skb->len - len;
+       int nsize;
        u16 flags;
+
+       nsize = skb_headlen(skb) - len;
+       if (nsize < 0)
+               nsize = 0;
 
        if (skb_cloned(skb) &&
            skb_is_nonlinear(skb) &&

--Chuck Ebbert  25-Oct-04  14:54:36

             reply	other threads:[~2004-10-25 18:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-25 18:53 Chuck Ebbert [this message]
2004-10-25 19:03 ` Justin Piszcz
  -- strict thread matches above, loose matches on Subject: below --
2004-10-25 10:48 Justin Piszcz
2004-10-25 11:33 ` Nick Piggin
2004-10-25 12:03   ` Justin Piszcz

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=200410251456_MC3-1-8D29-C332@compuserve.com \
    --to=76306.1226@compuserve.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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

all inboxes | Powered by JetHome®