From: Shuang Qiu <shuang.qiu@oracle.com>
To: linux-nfs@vger.kernel.org
Cc: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>,
yueyi Li <yueyi.li@oracle.com>
Subject: truncate() syscall against EFBIG errno issue over nfs filesystem
Date: Mon, 01 Jun 2015 19:29:00 +0800 [thread overview]
Message-ID: <556C41FC.3060902@oracle.com> (raw)
Hi guys,
In LTP truncate03 testcase
(https://github.com/linux-test-project/ltp/blob/master/testcases/kernel/syscalls/truncate/truncate03.c),the
sub-test which test the EFBUG errno will fail.
The test want to truncate the testfile to twice of the RLIMIT_FSIZE size.
According to the man page:
RLIMIT_FSIZE
The maximum size of files that the process may create.
Attempts to extend a file beyond this limit result in delivery of a
SIGXFSZ signal. By default, this signal terminates a
process, but a process can catch this signal instead, in which case the
relevant system call (e.g., write(2), truncate(2)) fails
with the error EFBIG.
We can get EFBIG on some other filesystem such like ext4,xfs.
But truncate will succeed unexpectedly if the testfile on nfs filesystem
after catch the SIGXFSZ signal.
I'm not sure if it is a bug for truncate(2) on nfs,or expected behavior?
Could someone help to have a look?
Thanks
Shuang
reply other threads:[~2015-06-01 11:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=556C41FC.3060902@oracle.com \
--to=shuang.qiu@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=stanislav.kholmanskikh@oracle.com \
--cc=yueyi.li@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.