From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: plars@austin.ibm.com (Paul Larson)
Cc: linux-kernel@vger.kernel.org (lkml),
torvalds@transmeta.com, ltp-list@lists.sourceforge.net (ltp)
Subject: Re: ftruncate
Date: Thu, 4 Oct 2001 22:35:18 +0100 (BST) [thread overview]
Message-ID: <E15pG9G-0004Jh-00@the-village.bc.nu> (raw)
In-Reply-To: <1002118765.12683.8.camel@plars.austin.ibm.com> from "Paul Larson" at Oct 03, 2001 02:19:11 PM
> that it does NOT pass on 2.4.10-ac4. It looks like the problem is with
> 2.4.11-pre1 and the testcase though if my man pages are right. The test
> is looking to get EACCESS back when the file is opened read only and
> ftruncate is called on it, but the man page says it should actually
> return EINVAL.
>
> A fixed version of this testcase will be in our next release. I know
> it's fairly trivial, but it would be nice to see this fix synced up with
> Linus's tree.
There are about 10 standards violations in the Linus tree against file
truncation behaviour (things like ftruncate > 2Gb without 64bit etc).
Merging them with the current scale of the fs/block changes in the current
Linus tree and their rate of change isnt feasible
prev parent reply other threads:[~2001-10-04 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 14:19 ftruncate Paul Larson
2001-10-04 21:35 ` Alan Cox [this message]
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=E15pG9G-0004Jh-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=plars@austin.ibm.com \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).