From: Phil Auld <pauld@egenera.com>
To: linux-kernel@vger.kernel.org
Subject: why is lseek broken (>= 2.4.11) ?
Date: Fri, 9 Aug 2002 08:49:15 -0400 [thread overview]
Message-ID: <20020809084915.P3542@vienna.EGENERA.COM> (raw)
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
next reply other threads:[~2002-08-09 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 12:49 Phil Auld [this message]
2002-08-09 20:48 ` why is lseek broken (>= 2.4.11) ? Andrew Morton
2002-08-09 21:13 ` Andries Brouwer
2002-08-09 21:42 ` Phil Auld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020809084915.P3542@vienna.EGENERA.COM \
--to=pauld@egenera.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox