From: David Miller <davem@davemloft.net>
To: ilpo.jarvinen@helsinki.fi
Cc: krkumar2@in.ibm.com, netdev@vger.kernel.org
Subject: Re: Assertions in latest kernels
Date: Wed, 23 Jan 2008 02:57:32 -0800 (PST) [thread overview]
Message-ID: <20080123.025732.200278761.davem@davemloft.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0801231043220.31652@kivilampi-30.cs.helsinki.fi>
From: "Ilpo_Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Wed, 23 Jan 2008 11:17:05 +0200 (EET)
> What a strange thing that it has been super quiet on this front
> until now everybody is seeing it, could there be something unrelated
> to TCP which has broken it all recently?
I think it is simply "capture effect".
One person reports the problem, and then others see it and
say "me too" because they were previously too busy to report
their instance of the problem.
Another thing is that a developer is sometimes working on something
and they do not want to pollute the bug reporting if the code they are
writing is what is causing the bug via some indirect corruptions or
whatever :-)
next prev parent reply other threads:[~2008-01-23 10:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 6:57 Assertions in latest kernels Krishna Kumar2
2008-01-23 7:52 ` Krishna Kumar2
2008-01-23 7:57 ` David Miller
2008-01-23 8:22 ` Krishna Kumar2
2008-01-23 9:17 ` Ilpo Järvinen
2008-01-23 10:57 ` David Miller [this message]
[not found] <OF6C895B68.E4A75EFD-ON652573D9.0034E821-652573D9.0034BF2E@in.ibm.com>
2008-01-23 9:53 ` Ilpo Järvinen
2008-01-23 10:38 ` Krishna Kumar2
2008-01-23 10:49 ` Ilpo Järvinen
2008-01-23 11:06 ` David Miller
2008-01-23 11:02 ` Krishna Kumar2
2008-01-23 11:42 ` 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=20080123.025732.200278761.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=krkumar2@in.ibm.com \
--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