From: Theodore Ts'o <tytso@mit.edu>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GIT PULL] gfs2 writepage fix
Date: Mon, 23 Jan 2023 11:03:07 -0500 [thread overview]
Message-ID: <Y86vu2WSGWCHpdJL@mit.edu> (raw)
In-Reply-To: <20230123100556.qxdjdmcms5ven52v@quack3>
On Mon, Jan 23, 2023 at 11:05:56AM +0100, Jan Kara wrote:
> Thanks for the heads up. So we had kind of a similar issue for ext4 but it
> got caught by Ted during his regression runs so we've basically done what
> GFS2 is doing for the merge window and now there's patchset pending to
> convert the data=journal path as well because as Andreas states in his
> changelog of the revert that's a bit more tricky. But at least for ext4
> the conversion of data=journal path resulted in much cleaner and shorter
> code.
https://thunk.org/tytso/images/firestarter-fs-development-without-testing.jpg
:-)
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andreas Gruenbacher <agruenba@redhat.com>,
David Howells <dhowells@redhat.com>,
Steve French <smfrench@gmail.com>,
Trond Myklebust <trondmy@hammerspace.com>,
Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>,
cluster-devel@redhat.com, linux-kernel@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] gfs2 writepage fix
Date: Mon, 23 Jan 2023 11:03:07 -0500 [thread overview]
Message-ID: <Y86vu2WSGWCHpdJL@mit.edu> (raw)
In-Reply-To: <20230123100556.qxdjdmcms5ven52v@quack3>
On Mon, Jan 23, 2023 at 11:05:56AM +0100, Jan Kara wrote:
> Thanks for the heads up. So we had kind of a similar issue for ext4 but it
> got caught by Ted during his regression runs so we've basically done what
> GFS2 is doing for the merge window and now there's patchset pending to
> convert the data=journal path as well because as Andreas states in his
> changelog of the revert that's a bit more tricky. But at least for ext4
> the conversion of data=journal path resulted in much cleaner and shorter
> code.
https://thunk.org/tytso/images/firestarter-fs-development-without-testing.jpg
:-)
- Ted
next prev parent reply other threads:[~2023-01-23 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 9:01 [Cluster-devel] [GIT PULL] gfs2 writepage fix Andreas Gruenbacher
2023-01-22 9:01 ` Andreas Gruenbacher
2023-01-22 20:05 ` [Cluster-devel] " Linus Torvalds
2023-01-22 20:05 ` Linus Torvalds
2023-01-23 10:05 ` [Cluster-devel] " Jan Kara
2023-01-23 10:05 ` Jan Kara
2023-01-23 16:03 ` Theodore Ts'o [this message]
2023-01-23 16:03 ` Theodore Ts'o
2023-01-22 20:20 ` [Cluster-devel] " pr-tracker-bot
2023-01-22 20:20 ` pr-tracker-bot
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=Y86vu2WSGWCHpdJL@mit.edu \
--to=tytso@mit.edu \
/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.