netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: David Miller <davem@davemloft.net>
Cc: brian.vowell@gmail.com, Andrew Morton <akpm@linux-foundation.org>,
	Netdev <netdev@vger.kernel.org>,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 10767] New: Seg Fault Instead of Swapping
Date: Wed, 4 Jun 2008 10:12:04 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0806040943120.16057@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <20080603.163518.153888925.davem@davemloft.net>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1124 bytes --]

On Tue, 3 Jun 2008, David Miller wrote:

> From: "Ilpo_Järvinen" <ilpo.jarvinen@helsinki.fi>
> Date: Mon, 26 May 2008 14:24:33 +0300 (EEST)
> 
> Ilpo, do you want me to apply this to net-2.6?

Yes thanks, it is necessary to keep the state consistent (it also explains 
some .22/23 time left_out warn_ons too which were mysterious back then).
Also -stable (I guess it would be necessary to almost any older stable
too though some older ones might want to sync left_out on that same place 
too).

It was nice that this path was also triggered while running the TCP 
debug patch (I haven't gotten a one in here), otherwise we would never
have known though I started to suspect that such path existed once I
tried to analyze those left_out problems (before it got dropped 
altogether), but I just couldn't find the problem because it lies on 
such "error path" which was too easy to overlook.

I also finally have found the cause to the !sacked_out && fackets_out
trap :-). ...I'll post the fix to that later today to relevant parties.

> > [PATCH] [TCP]: Fix inconsistency source (CA_Open only when !tcp_left_out(tp))


-- 
 i.

  reply	other threads:[~2008-06-04  7:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10767-10286@http.bugzilla.kernel.org/>
2008-05-21 17:57 ` [Bugme-new] [Bug 10767] New: Seg Fault Instead of Swapping Andrew Morton
     [not found]   ` <cf4145200805211140o3b2287dcsc57f8a78aa48a99d@mail.gmail.com>
2008-05-21 18:53     ` Andrew Morton
2008-05-21 20:18     ` Ilpo Järvinen
     [not found]       ` <cf4145200805211345y3b00d209o58e11a7b553cdfc6@mail.gmail.com>
2008-05-23 10:25         ` Ilpo Järvinen
     [not found]           ` <cf4145200805230906k34a0452at773e840b791e6b0a@mail.gmail.com>
     [not found]             ` <cf4145200805231024w2e735fb8ifecf7e2e1bab5957@mail.gmail.com>
2008-05-23 18:01               ` Ilpo Järvinen
     [not found]                 ` <cf4145200805231126y401c2454w97e5305346aa8acd@mail.gmail.com>
2008-05-24  8:57                   ` Ilpo Järvinen
     [not found]                     ` <cf4145200805240706p2eb54e9ei51bc33f782ff5aef@mail.gmail.com>
2008-05-26 11:24                       ` Ilpo Järvinen
2008-06-03 23:35                         ` David Miller
2008-06-04  7:12                           ` Ilpo Järvinen [this message]
2008-06-04 18:20                             ` David Miller
2008-05-26 11:33             ` Ilpo Järvinen

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.0806040943120.16057@wrl-59.cs.helsinki.fi \
    --to=ilpo.jarvinen@helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=brian.vowell@gmail.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=davem@davemloft.net \
    --cc=netdev@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).