lost socket
From: Ricky Beam (jfbeam_at_bluetronic.net)
Date: 08/27/03
- Previous message: Alan Cox: "Re: [PATCH] Backport recent IDE updates, take 2"
- Next in thread: Ricky Beam: "/proc/net/* read drops data (was: lost socket)"
- Reply: Ricky Beam: "/proc/net/* read drops data (was: lost socket)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 27 Aug 2003 17:27:32 -0400 (EDT) To: Linux Kernel Mail List <linux-kernel@vger.kernel.org>
It would appear the kernel is not properly reporting all the active sockets.
I noticed this in 2.5.70 while checking netflow collection... udp port 9800
is bound and actively receiving traffic, however, nothing reports it's
existance. 2.6.0-test4 still has this bug.
This smells like a simple "off by one" bug, but I've been too busy to go
look at the code.
--Ricky
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Previous message: Alan Cox: "Re: [PATCH] Backport recent IDE updates, take 2"
- Next in thread: Ricky Beam: "/proc/net/* read drops data (was: lost socket)"
- Reply: Ricky Beam: "/proc/net/* read drops data (was: lost socket)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]