Date: Fri, 9 Aug 2002 08:49:15 -0400
From: Phil Auld <pauld@egenera.com>
To: linux-kernel@vger.kernel.org
Subject: why is lseek broken (>= 2.4.11) ?
Message-ID: <20020809084915.P3542@vienna.EGENERA.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1108
Lines: 35

Hi folks,

There was a brief thread a couple of months ago about the change in 
lseek for block devices. The thread is here:

http://marc.theaimsgroup.com/?t=102406030100003&r=1&w=2

The change, which looks to have come in with 2.4.11, returns
EINVAL from an lseek on a block device attempting to set pos past 
the size of the device. 
 
This causes current versions glibc to exhibit non-SUS3 lseek behavior.

Are there plans to revert this? It seems that this is something that 
should be addressed in glibc first and then have the kernel change. 

There is no resolution in the thread above, nor is there any 
justification for the change. It just peters out.

Any thoughts?

Thanks,

Phil


-- 
Philip R. Auld, Ph.D.                  Technical Staff 
Egenera Corp.                        pauld@egenera.com
165 Forest St., Marlboro, MA 01752       (508)858-2600
-
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/