From: Andries.Brouwer@cwi.nl
Date: Sat, 15 Jun 2002 16:20:11 +0200 (MEST)
Message-Id: <UTC200206151420.g5FEKBF25783.aeb@smtp.cwi.nl>
To: adilger@clusterfs.com, tomaz.susnik@hermes.si
Subject: Re: 2.4.18 kernel lseek() bug
Cc: linux-kernel@vger.kernel.org
Sender: linux-kernel-owner@vger.kernel.org

    >      a call to lseek() fails with EINVAL under the following conditions:
    >         - it is called on a disk device file
    >         - required offset is larger than the target disk device size

    Is this behaviour mandated in a standard, or is it just different from
    previous behaviour?  I'm not saying it _isn't_ a bug, but I don't see
    how seeking past the end of a block device is very useful.

I know many programs that use this. They seek and do not expect
an error, because the standard says no error is to be expected,
and then try to read or write.

Let me quote POSIX 1003.1-2001.

...
The lseek() function shall allow the file offset to be set beyond the
end of the existing data in the file.
...

[EINVAL] 
          The whence argument is not a proper value, or the resulting
          file offset would be negative for a regular file, block special
          file, or directory. 


Andries
-
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/