From: Arjan van de Ven <arjan@linux.intel.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, ilpo.jarvinen@helsinki.fi
Subject: Re: Three TCP/IP warnings in 2.6.25-rc7-git1
Date: Wed, 02 Apr 2008 22:40:47 -0700 [thread overview]
Message-ID: <47F46DDF.90304@linux.intel.com> (raw)
In-Reply-To: <20080402.222846.92587028.davem@davemloft.net>
David Miller wrote:
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Wed, 02 Apr 2008 22:21:09 -0700
>
>> It would be not so nice to ship a 2.6.25 that triggers these frequently,
>> it has the risk of causing many user bugreports to this list and other
>> places...
>
> I wouldn't call it frequently, on at least an individual basis,
> because nobody we try to get feedback from can reproduce this
> reliably. That's the only reason this isn't fixed yet, despite
> all of Ilpo's efforts.
(first of all I'm not trying to say you guys aren't trying; I know chasing such stuff is
really hard; I'm just trying to help by giving information on when/what it happens, and that it hasn't been
reported prior to 2.6.24-rc4 for example)
What I meant by frequently is that the fedora rawhide users have seen this 24 times
in the last 7 days. The Fedora rawhide userbase is a lot smaller than the total userbase of
what will be the 2.6.25 kernel, so I suspect that the total number of people who'll find
this at least once when 2.6.25 goes out is likely to be much higher...
(to counter that.. it's a WARN_ON so it's a good question if those people will actually see it and
then report it)
I didn't mean it in the sense that one person sees it all the time.
(Which would obviously MUCH nicer debugging wise)
If there's a way to add more WARN_ON's to places that are suspect that would work; via kerneloops.org
there'll be at least statistical information if those places hit (and possibly they can be correlated
to these warnings happening). This doesn't mean you'll have someone who can try this and say it goes away,
but it also means the testbase for this is a lot wider... eg when the fish are rare, cast a wider net.
next prev parent reply other threads:[~2008-04-03 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 21:05 Two TCP/IP warnings in 2.6.25-rc7-git1 Arjan van de Ven
2008-04-03 5:21 ` Three " Arjan van de Ven
2008-04-03 5:28 ` David Miller
2008-04-03 5:40 ` Arjan van de Ven [this message]
2008-04-03 5:56 ` Denys Fedoryshchenko
2008-04-03 9:53 ` Ilpo Järvinen
2008-04-03 12:14 ` Denys Fedoryshchenko
2008-04-03 13:11 ` 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=47F46DDF.90304@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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).