From: Eric Sandeen <sandeen@sandeen.net>
To: xfs mailing list <xfs@oss.sgi.com>
Subject: [PATCH] xfs_io: actually issue 0 size writes
Date: Thu, 13 Aug 2009 17:15:50 -0500 [thread overview]
Message-ID: <4A849096.1010600@sandeen.net> (raw)
While testing some stuff in generic_write_checks() in the
kernel I realized that you can't actually use xfs_io to send
a 0-byte write in. This is actually a condition worth testing:
If count is zero and fd refers to a regular file,
then write() may return a failure status if one of
the errors below is detected. If no errors are
detected, 0 will be returned without causing any
other effect.
So fix that up.
Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
---
iff --git a/io/pwrite.c b/io/pwrite.c
index 54c3f78..26a7850 100644
--- a/io/pwrite.c
+++ b/io/pwrite.c
@@ -163,7 +163,7 @@ write_buffer(
int ops = 0;
*total = 0;
- while (count > 0) {
+ while (count >= 0) {
if (fd > 0) { /* input file given, read buffer first */
if (read_buffer(fd, skip + *total, bs, &bar, 0, 1) < 0)
break;
@@ -182,6 +182,8 @@ write_buffer(
break;
offset += bytes;
count -= bytes;
+ if (count == 0)
+ break;
}
return ops;
}
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-08-13 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 22:15 Eric Sandeen [this message]
2009-08-13 22:52 ` [PATCH] xfs_io: actually issue 0 size writes Felix Blyakher
2009-08-14 0:15 ` Eric Sandeen
2009-08-26 22:11 ` Christoph Hellwig
2009-08-26 23:26 ` Eric Sandeen
[not found] <139598026.1934901250211190252.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-14 0:56 ` Lachlan McIlroy
2009-08-14 1:34 ` Eric Sandeen
[not found] <148381776.1936161250214905902.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2009-08-14 1:55 ` Lachlan McIlroy
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=4A849096.1010600@sandeen.net \
--to=sandeen@sandeen.net \
--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 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.