From: Andi Kleen <andi@firstfloor.org>
To: Tejun Heo <tj@kernel.org>
Cc: Junichi Nomura <j-nomura@ce.jp.nec.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"andi@firstfloor.org" <andi@firstfloor.org>,
"fengguang.wu@intel.com" <fengguang.wu@intel.com>,
"tony.luck@intel.com" <tony.luck@intel.com>,
"liwanp@linux.vnet.ibm.com" <liwanp@linux.vnet.ibm.com>,
"david@fromorbit.com" <david@fromorbit.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH 1/1] fs: global sync to not clear error status of individual inodes
Date: Tue, 15 Sep 2015 18:52:50 +0200 [thread overview]
Message-ID: <20150915165250.GC1747@two.firstfloor.org> (raw)
In-Reply-To: <20150915152006.GD2905@mtj.duckdns.org>
> Is this an actual problem? Write errors usually indicate that the
There are transaction systems that need to track errors at the level
of the individual IO. So yes we should guarantee that if a particular
sync failed an error is always returned.
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-09-15 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-15 9:46 [PATCH 0/1] Fix false-negative error reporting from fsync/fdatasync Junichi Nomura
2015-09-15 9:49 ` Test program: check if fsync() can detect I/O error (1/2) Junichi Nomura
2015-09-15 9:52 ` Test program: check if fsync() can detect I/O error (2/2) Junichi Nomura
2015-09-15 9:54 ` [PATCH 1/1] fs: global sync to not clear error status of individual inodes Junichi Nomura
2015-09-15 14:37 ` Andi Kleen
2015-09-15 22:02 ` Andrew Morton
2015-09-16 0:45 ` Junichi Nomura
2015-09-16 10:45 ` xfstests: test data-writeback error detection with fsync Junichi Nomura
2015-09-15 15:20 ` [PATCH 1/1] fs: global sync to not clear error status of individual inodes Tejun Heo
2015-09-15 16:52 ` Andi Kleen [this message]
2015-09-16 0:59 ` Junichi Nomura
2015-09-16 8:39 ` [PATCH v2] " Junichi Nomura
2015-09-16 17:47 ` 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=20150915165250.GC1747@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=tj@kernel.org \
--cc=tony.luck@intel.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).