why is lseek broken (>= 2.4.11) ?

• Next message: Thomas Hood: "[PATCH] Fix error in pnpbios escd read routine"
• Previous message: Gilad Ben-Yossef: "Re: device driver / char module interrupt vector -> user space code"
• Next in thread: Andrew Morton: "Re: why is lseek broken (>= 2.4.11) ?"
• Reply: Andrew Morton: "Re: why is lseek broken (>= 2.4.11) ?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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/

• Next message: Thomas Hood: "[PATCH] Fix error in pnpbios escd read routine"
• Previous message: Gilad Ben-Yossef: "Re: device driver / char module interrupt vector -> user space code"
• Next in thread: Andrew Morton: "Re: why is lseek broken (>= 2.4.11) ?"
• Reply: Andrew Morton: "Re: why is lseek broken (>= 2.4.11) ?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:19 EST