From: "David S. Miller" <davem@redhat.com>
To: fabien.ribes@cgey.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in sock_poll
Date: Fri, 18 Jan 2002 02:55:54 -0800 (PST) [thread overview]
Message-ID: <20020118.025554.133432828.davem@redhat.com> (raw)
In-Reply-To: <3C47E46C.2E322EC6@cgey.com>
In-Reply-To: <3C470105.ED9DDCE@cgey.com> <20020117.131224.108809922.davem@redhat.com> <3C47E46C.2E322EC6@cgey.com>
From: Fabien Ribes <fabien.ribes@cgey.com>
Date: Fri, 18 Jan 2002 09:01:32 +0000
"David S. Miller" wrote:
>
> Can you reproduce this with a more recent kernel? Anything
> >=2.4.9 (this includes all Red Hat errata kernels therefore)
> would be sufficient.
The kernel used is customized in many ways, it is a long work to upgrade
Then I can't help you... there have probably been many
networking bugs fixed since 2.4.9
next prev parent reply other threads:[~2002-01-18 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 16:51 Oops in sock_poll Fabien Ribes
2002-01-17 21:12 ` David S. Miller
2002-01-18 9:01 ` Fabien Ribes
2002-01-18 10:55 ` David S. Miller [this message]
2002-01-19 18:41 ` kuznet
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=20020118.025554.133432828.davem@redhat.com \
--to=davem@redhat.com \
--cc=fabien.ribes@cgey.com \
--cc=linux-kernel@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