From: Zach Brown <zach.brown@oracle.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: suparna@in.ibm.com, linux-kernel@vger.kernel.org,
"'Andrew Morton'" <akpm@osdl.org>,
pbadari@gmail.com
Subject: Re: [patch] bug fix in dio handling write error - v2
Date: Mon, 20 Mar 2006 13:28:21 -0800 [thread overview]
Message-ID: <441F1E75.8050803@oracle.com> (raw)
In-Reply-To: <200603192227.k2JMRNg30260@unix-os.sc.intel.com>
> Taking one of your earlier idea, how about the following patch: separating
> out IO completion code from partial IO tracking?
I like that, and I think it closes the lost write error hole. Could we
call it something like io_errno, though? "completion_code" to me sounds
like -ve errno or +ve bytes read.
I think there are still bugs dealing with errors, but I guess we can
tackle them with seperate patches.
- z
next prev parent reply other threads:[~2006-03-20 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 9:27 [patch] bug fix in dio handling write error - v2 Chen, Kenneth W
2006-03-19 11:54 ` Suparna Bhattacharya
2006-03-19 22:27 ` Chen, Kenneth W
2006-03-20 21:28 ` Zach Brown [this message]
2006-03-21 7:06 ` Suparna Bhattacharya
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=441F1E75.8050803@oracle.com \
--to=zach.brown@oracle.com \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.com \
--cc=suparna@in.ibm.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