From: Paul Larson <plars@austin.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>, torvalds@transmeta.com
Cc: ltp <ltp-list@lists.sourceforge.net>
Subject: ftruncate
Date: 03 Oct 2001 14:19:11 +0000 [thread overview]
Message-ID: <1002118765.12683.8.camel@plars.austin.ibm.com> (raw)
One of the testcases we have in the Linux Test Project, ftruncate03,
does some negative testing for the ftruncate system call. It has
previously passed, and even passes on 2.4.11-pre1, but I noticed today
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.
Thanks,
Paul Larson
next reply other threads:[~2001-10-03 19:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-03 14:19 Paul Larson [this message]
2001-10-04 21:35 ` ftruncate Alan Cox
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=1002118765.12683.8.camel@plars.austin.ibm.com \
--to=plars@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-list@lists.sourceforge.net \
--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).