lkml.org 
[lkml]   [2002]   [Aug]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: why is lseek broken (>= 2.4.11) ?
Phil Auld wrote:
>
> 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.

What should the behaviour be? The lseek should succeed,
but subsequent reads and writes return zero?
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:27    [W:0.026 / U:1.520 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site