LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeff Chua <jeff.chua.linux@gmail.com>
To: Patrick McHardy <kaber@trash.net>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
lkml <linux-kernel@vger.kernel.org>,
Krzysztof Piotr Oledzki <ole@ans.pl>,
"David S. Miller" <davem@davemloft.net>,
cups-bugs <cups-bugs@easysw.com>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: cups slow on linux-2.6.24
Date: Sun, 10 Feb 2008 23:06:35 +0800 (SGT) [thread overview]
Message-ID: <Pine.LNX.4.64.0802102257420.14442@boston.corp.fedex.com> (raw)
On Feb 5, 2008 9:47 PM, Patrick McHardy wrote:
>> On Feb 5, 2008 4:16 PM, Jozsef Kadlecsik wrote:
>> Patrick, I suppose you need a patch against the latest git, don't you?
> Yes, please. I'll take you first patch for -stable though if you
> send me a Signed-off-by: line.
Please note the lastest git commit is missing one part (which was in
Jozsef's original patch).
commit b2155e7f70b3f058efe94c0c459db023b05057bd
Author: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Date: Thu Feb 7 17:54:56 2008 -0800
[NETFILTER]: nf_conntrack: TCP conntrack reopening fix
I've tested the following missing patch, and it solves the cups slow
printing problem.
Thanks,
Jeff
--- a/net/netfilter/nf_conntrack_proto_tcp.c.org 2008-02-10 22:45:49 +0800
+++ a/net/netfilter/nf_conntrack_proto_tcp.c 2008-02-10 22:45:56 +0800
@@ -945,7 +945,7 @@
ct->proto.tcp.state = new_state;
if (old_state != new_state
- && new_state == TCP_CONNTRACK_CLOSE)
+ && new_state == TCP_CONNTRACK_FIN_WAIT)
ct->proto.tcp.seen[dir].flags |= IP_CT_TCP_FLAG_CLOSE_INIT;
timeout = ct->proto.tcp.retrans >= nf_ct_tcp_max_retrans
&& tcp_timeouts[new_state] > nf_ct_tcp_timeout_max_retrans
next reply other threads:[~2008-02-10 15:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 15:06 Jeff Chua [this message]
2008-02-14 15:02 ` Jozsef Kadlecsik
2008-02-14 22:50 ` David Miller
2008-02-15 1:44 ` Patrick McHardy
-- strict thread matches above, loose matches on Subject: below --
2008-02-05 1:17 Jeff Chua
2008-02-05 8:16 ` Jozsef Kadlecsik
2008-02-05 13:47 ` Patrick McHardy
[not found] <Pine.LNX.4.64.0802042226340.28805@boston.corp.fedex.com>
2008-02-04 20:17 ` Jozsef Kadlecsik
2008-01-28 22:41 Jeff Chua
2008-01-28 22:56 ` Krzysztof Oledzki
2008-01-28 23:55 ` Jeff Chua
2008-01-29 10:53 ` Jozsef Kadlecsik
[not found] ` <b6a2187b0801291924k15f883aeg54f704156e4f2e3e@mail.gmail.com>
2008-01-30 13:47 ` Patrick McHardy
2008-01-31 2:23 ` Jeff Chua
[not found] ` <b6a2187b0801301826l5a50ce84p7d5dce3d0a74b3c0@mail.gmail.com>
2008-01-31 2:41 ` Patrick McHardy
2008-01-31 3:21 ` Jeff Chua
2008-01-31 3:25 ` Patrick McHardy
2008-01-31 5:01 ` Jeff Chua
2008-01-31 10:40 ` Jozsef Kadlecsik
2008-01-31 18:53 ` Patrick McHardy
2008-02-01 0:47 ` David Newall
2008-02-01 2:12 ` David Miller
2008-02-01 6:07 ` David Newall
2008-02-01 6:10 ` Patrick McHardy
2008-02-01 5:28 ` Jeff Chua
2008-02-02 14:44 ` Jozsef Kadlecsik
2008-02-03 16:08 ` Jeff Chua
2008-01-27 23:18 Jeff Chua
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=Pine.LNX.4.64.0802102257420.14442@boston.corp.fedex.com \
--to=jeff.chua.linux@gmail.com \
--cc=cups-bugs@easysw.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
--cc=torvalds@linux-foundation.org \
--subject='Re: cups slow on linux-2.6.24' \
/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
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).