From: "Theodore Ts'o" <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Gabriel Krisman Bertazi <krisman@collabora.com>,
jack@suse.com, viro@zeniv.linux.org.uk, amir73il@gmail.com,
dhowells@redhat.com, darrick.wong@oracle.com, khazhy@google.com,
linux-fsdevel@vger.kernel.org, kernel@collabora.com
Subject: Re: [RFC] Filesystem error notifications proposal
Date: Tue, 9 Feb 2021 12:57:08 -0500 [thread overview]
Message-ID: <YCLM9NPSwsWFPu4t@mit.edu> (raw)
In-Reply-To: <20210209085501.GS4626@dread.disaster.area>
On Tue, Feb 09, 2021 at 07:55:01PM +1100, Dave Chinner wrote:
>
> That means we have to work together to find common ground and a
> solution that works for everyone. What I've suggested allows all
> filesystems to supply the same information for the same events. It
> also allows filesystems to include their own private diagnostic
> information appended to the generic message, thereby fulfulling both
> the goals of both David Howells' original patchset and Gabriel's
> derived ext4 specific patchset.
So the simple common ground would be a plain text message, which is
what *I* had suggested. But I saw you requesting some complex object
based system which XFS has.
I think if we want to keep something that is common, it's going to
have to be kept simple. Do you not agree?
- Ted
next prev parent reply other threads:[~2021-02-09 18:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 20:13 [RFC] Filesystem error notifications proposal Gabriel Krisman Bertazi
2021-01-21 4:01 ` Viacheslav Dubeyko
2021-01-21 11:44 ` Jan Kara
2021-01-21 13:27 ` Amir Goldstein
2021-01-21 18:56 ` Gabriel Krisman Bertazi
2021-01-21 22:44 ` Theodore Ts'o
2021-01-22 0:44 ` Gabriel Krisman Bertazi
2021-01-22 7:36 ` Amir Goldstein
2021-02-02 20:51 ` Gabriel Krisman Bertazi
2021-01-28 22:28 ` Theodore Ts'o
2021-02-02 20:26 ` Gabriel Krisman Bertazi
2021-02-02 22:34 ` Theodore Ts'o
2021-02-08 18:49 ` Gabriel Krisman Bertazi
2021-02-08 22:19 ` Dave Chinner
2021-02-09 1:08 ` Theodore Ts'o
2021-02-09 5:12 ` Khazhismel Kumykov
2021-02-09 8:55 ` Dave Chinner
2021-02-09 17:57 ` Theodore Ts'o [this message]
2021-02-10 0:52 ` Darrick J. Wong
2021-02-10 2:21 ` Theodore Ts'o
2021-02-10 2:32 ` Darrick J. Wong
2021-02-09 17:35 ` Jan Kara
2021-02-10 0:22 ` Darrick J. Wong
2021-02-10 7:46 ` Dave Chinner
2021-02-10 0:49 ` Darrick J. Wong
2021-02-10 0:09 ` Darrick J. Wong
2021-02-10 7:23 ` Amir Goldstein
2021-02-10 23:29 ` Gabriel Krisman Bertazi
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=YCLM9NPSwsWFPu4t@mit.edu \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.com \
--cc=kernel@collabora.com \
--cc=khazhy@google.com \
--cc=krisman@collabora.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.