From: Jamie Lokier <jamie@shareable.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Denis Karpov <ext-denis.2.karpov@nokia.com>,
axboe@kernel.dk, hirofumi@mail.parknet.co.jp,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, adrian.hunter@nokia.com,
artem.bityutskiy@nokia.com
Subject: Re: [PATCH 0/4] FS: userspace notification of errors
Date: Thu, 4 Jun 2009 02:59:35 +0100 [thread overview]
Message-ID: <20090604015935.GA30472@shareable.org> (raw)
In-Reply-To: <20090603115611.6bbbaf55.akpm@linux-foundation.org>
Andrew Morton wrote:
> The "unclean" term doesn't seem a good fit. It usually means "has
> in-memory data which needs writing back". But here you've redefined
> "unclean" to mean "got an IO error" or "detected metadata
> inconsistency", or perhaps "dunno, please run fsck to find out". This
> all should be spelled out in exacting detail and thought about, please.
I agree. "unclean" (or "dirty") should be reserved for indicating
that the filesystem has been modified, that is, files written to etc.
Use another term like "fault" or "error"?
-- Jamie
next prev parent reply other threads:[~2009-06-04 1:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:05 [PATCH 0/4] FS: userspace notification of errors Denis Karpov
2009-06-03 15:05 ` [PATCH 1/4] FS: filesystem corruption notification Denis Karpov
2009-06-03 15:05 ` [PATCH 2/4] FAT: generalize errors and warning printing Denis Karpov
2009-06-03 15:05 ` [PATCH 3/4] FAT: add 'notify' mount option Denis Karpov
2009-06-03 18:59 ` Andrew Morton
2009-06-03 15:05 ` [PATCH 4/4] EXT2: " Denis Karpov
2009-06-03 19:00 ` Andrew Morton
2009-06-10 21:03 ` Pavel Machek
2009-06-03 18:58 ` [PATCH 1/4] FS: filesystem corruption notification Andrew Morton
2009-06-03 15:36 ` [PATCH 0/4] FS: userspace notification of errors Eric Sandeen
2009-06-03 18:56 ` Andrew Morton
2009-06-04 1:59 ` Jamie Lokier [this message]
2009-06-04 5:57 ` Artem Bityutskiy
2009-06-04 5:57 ` Artem Bityutskiy
2009-06-04 14:27 ` Denis Karpov
2009-06-10 21:03 ` Pavel Machek
2009-06-10 21:03 ` Pavel Machek
2009-06-10 21:05 ` Pavel Machek
2009-06-04 12:53 ` Kay Sievers
2009-06-04 12:53 ` Kay Sievers
2009-06-04 14:29 ` Russell Cattelan
2009-06-05 7:25 ` Jon Masters
2009-06-05 11:07 ` Artem Bityutskiy
2009-06-05 11:07 ` Artem Bityutskiy
2009-06-05 11:51 ` Denis Karpov
2009-06-05 13:06 ` Kay Sievers
2009-06-05 13:06 ` Kay Sievers
2009-06-05 13:06 ` Kay Sievers
2009-06-09 13:49 ` Jan Kara
2009-06-03 22:30 ` Jan Kara
2009-06-04 6:10 ` Artem Bityutskiy
2009-06-04 6:10 ` Artem Bityutskiy
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=20090604015935.GA30472@shareable.org \
--to=jamie@shareable.org \
--cc=adrian.hunter@nokia.com \
--cc=akpm@linux-foundation.org \
--cc=artem.bityutskiy@nokia.com \
--cc=axboe@kernel.dk \
--cc=ext-denis.2.karpov@nokia.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.