From owner-freebsd-alpha Tue Oct 10 14:44:47 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id BF54A37B503 for ; Tue, 10 Oct 2000 14:44:44 -0700 (PDT) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA07222 for ; Tue, 10 Oct 2000 17:44:44 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.0/8.9.1) id e9ALiiI71184; Tue, 10 Oct 2000 17:44:44 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 10 Oct 2000 17:44:43 -0400 (EDT) To: freebsd-alpha@freebsd.org Subject: can read return MORE than you asked for? X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14819.36145.726782.115049@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org When looking into the "swapinfo:cannot read blmeta_t" problem, I discovered that reading /dev/kmem seems to be somewhat broken: <..> lseek(4,0xfffffe00006b8428,-3399988123389603632) = 7046184 (0x6b8428) read(0x4,0x11ffa2d0,0x8) = 16 (0x10) <..> Note the return value of read -- 2x what we asked for! I think I just entered the twilight zone. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message