From: Jeff Liu <jeff.liu@oracle.com>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: [PATCH] xfs: don't return 0 if generic_segment_checks() find nothing to write
Date: Fri, 12 Apr 2013 23:48:28 +0800 [thread overview]
Message-ID: <51682CCC.308@oracle.com> (raw)
From: Jie Liu <jeff.liu@oracle.com>
At xfs_file_aio_write(), we just return 0 which means a successfully operation if the ocount
is evaluated to 0 at generic_segment_checks(). Generally, it'll occurred if the specified
write count is 0 from the user space. However, for example, if the given offset is over the
maximum file size limitation although nothing would be written into the file, in this case,
the underlying file system should detect this issue and return a proper errno instead.
Hence, the beginning pre-checking up against ocount would conceal some real cause and confuse
the user space program maybe.
To fix it, we can delay the write count verification until xfs_file_aio_write_checks() is done.
This test is performed on 32-bit system without CONFIG_LBADF is enabled.
Before patching:
xfs_io -f -c "pwrite 17592186040320 0" /storage/test_file
wrote 0/0 bytes at offset 17592186040320
0.000000 bytes, 0 ops; 0.0000 sec (0.000000 bytes/sec and 0.0000 ops/sec)
After patching:
xfs_io -f -c "pwrite 17592186040320 0" /storage/test_file
pwrite64: File too large
Signed-off-by: Jie Liu <jeff.liu@oracle.com>
---
fs/xfs/xfs_file.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/fs/xfs/xfs_file.c b/fs/xfs/xfs_file.c
index f03bf1a..f8a933e 100644
--- a/fs/xfs/xfs_file.c
+++ b/fs/xfs/xfs_file.c
@@ -671,6 +671,9 @@ xfs_file_dio_aio_write(
if (ret)
goto out;
+ if (ocount == 0)
+ goto out;
+
if (mapping->nrpages) {
ret = -filemap_write_and_wait_range(VFS_I(ip)->i_mapping,
pos, -1);
@@ -725,6 +728,9 @@ xfs_file_buffered_aio_write(
if (ret)
goto out;
+ if (ocount == 0)
+ goto out;
+
/* We can write back this queue in page reclaim */
current->backing_dev_info = mapping->backing_dev_info;
@@ -772,9 +778,6 @@ xfs_file_aio_write(
if (ret)
return ret;
- if (ocount == 0)
- return 0;
-
sb_start_write(inode->i_sb);
if (XFS_FORCED_SHUTDOWN(ip->i_mount)) {
--
1.7.9.5
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-04-12 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 15:48 Jeff Liu [this message]
2013-04-16 18:26 ` [PATCH] xfs: don't return 0 if generic_segment_checks() find nothing to write Ben Myers
2013-04-16 18:35 ` Jeff Liu
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=51682CCC.308@oracle.com \
--to=jeff.liu@oracle.com \
--cc=xfs@oss.sgi.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