From: Andrew Morton <akpm@osdl.org>
To: Chris Mason <mason@suse.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] O_SYNC error handling fix
Date: Mon, 16 Jan 2006 12:11:49 -0800 [thread overview]
Message-ID: <20060116121149.1a12b4cf.akpm@osdl.org> (raw)
In-Reply-To: <200601160926.15701.mason@suse.com>
Chris Mason <mason@suse.com> wrote:
>
> I can special case the -EIO check for just O_SYNC. I think that along
> with changing around the O_DIRECT bits will make us both happy?
I guess so...
It seems I'm full of crap anyway. We already return -EFOO on failing O_SYNC
writes, no?
prev parent reply other threads:[~2006-01-16 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 0:43 [PATCH] O_SYNC error handling fix Chris Mason
2006-01-16 7:58 ` Andrew Morton
2006-01-16 14:26 ` Chris Mason
2006-01-16 20:11 ` Andrew Morton [this message]
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=20060116121149.1a12b4cf.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mason@suse.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;
as well as URLs for NNTP newsgroup(s).