From: Tejun Heo <htejun@gmail.com>
To: zach.brown@oracle.com, pbadari@us.ibm.com, suparna@in.ibm.com,
jmoyer@redhat.com, akpm@osdl.org, cwyang@aratech.co.kr,
linux-kernel@vger.kernel.org, htejun@gmail.com
Cc: Tejun Heo <htejun@gmail.com>
Subject: [PATCH 2/5] direct-io: fix dio_complete() errno passing in sync completion path
Date: Thu, 9 Nov 2006 10:16:11 +0900 [thread overview]
Message-ID: <11630349712471-git-send-email-htejun@gmail.com> (raw)
In-Reply-To: <11630349713427-git-send-email-htejun@gmail.com>
In synchronous completion path, the number of transferred bytes is
always passed to dio_complete() as @bytes argument whether the
transfer succeeded or not. Fix it.
Signed-off-by: Tejun Heo <htejun@gmail.com>
---
fs/direct-io.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/fs/direct-io.c b/fs/direct-io.c
index 25721b2..c85aee3 100644
--- a/fs/direct-io.c
+++ b/fs/direct-io.c
@@ -1138,10 +1138,11 @@ direct_io_worker(int rw, struct kiocb *i
if (rw == READ && (offset + transferred > i_size))
transferred = i_size - offset;
}
- dio_complete(dio, offset, transferred);
if (ret == 0)
ret = transferred;
+ dio_complete(dio, offset, ret);
+
/* We could have also come here on an AIO file extend */
if (!is_sync_kiocb(iocb) && (rw & WRITE) &&
ret >= 0 && dio->result == dio->size)
--
1.4.3.3
next prev parent reply other threads:[~2006-11-09 1:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 1:16 [RESEND PATCHSET] direct-io: unify asyn/sync completion paths and fix completion bugs Tejun Heo
2006-11-09 1:16 ` Tejun Heo [this message]
2006-11-09 1:16 ` [PATCH 1/5] direct-io: fix page_errors handling Tejun Heo
2006-11-09 1:16 ` [PATCH 3/5] direct-io: factor out dio_determine_result() Tejun Heo
2006-11-09 1:16 ` [PATCH 4/5] direct-io: unify sync and async completion paths Tejun Heo
2006-11-09 1:16 ` [PATCH 5/5] direct-io: fix double completion on partially valid async requests Tejun Heo
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=11630349712471-git-send-email-htejun@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@osdl.org \
--cc=cwyang@aratech.co.kr \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=suparna@in.ibm.com \
--cc=zach.brown@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.