From: Christoph Hellwig <hch@lst.de>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 1/1] Revert "iomap: fall back to buffered writes for invalidation failures"
Date: Mon, 14 Feb 2022 14:42:06 +0100 [thread overview]
Message-ID: <20220214134206.GA29930@lst.de> (raw)
In-Reply-To: <YgowAl01rq5A8Sil@google.com>
Let me repeat myself: Please send a proper bug report to the linux-ext4
list. Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Lee Jones <lee.jones@linaro.org>
Cc: Matthew Wilcox <willy@infradead.org>,
"Darrick J. Wong" <djwong@kernel.org>,
linux-kernel@vger.kernel.org, Stable <stable@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>,
Dave Chinner <dchinner@redhat.com>,
Goldwyn Rodrigues <rgoldwyn@suse.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Bob Peterson <rpeterso@redhat.com>,
Damien Le Moal <damien.lemoal@wdc.com>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Gruenbacher <agruenba@redhat.com>,
Ritesh Harjani <riteshh@linux.ibm.com>,
Johannes Thumshirn <jth@kernel.org>,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, cluster-devel@redhat.com,
syzbot+0ed9f769264276638893@syzkaller.appspotmail.com
Subject: Re: [PATCH 1/1] Revert "iomap: fall back to buffered writes for invalidation failures"
Date: Mon, 14 Feb 2022 14:42:06 +0100 [thread overview]
Message-ID: <20220214134206.GA29930@lst.de> (raw)
In-Reply-To: <YgowAl01rq5A8Sil@google.com>
Let me repeat myself: Please send a proper bug report to the linux-ext4
list. Thanks!
next prev parent reply other threads:[~2022-02-14 13:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 8:52 [Cluster-devel] [PATCH 1/1] Revert "iomap: fall back to buffered writes for invalidation failures" Lee Jones
2022-02-09 8:52 ` Lee Jones
2022-02-09 10:45 ` [Cluster-devel] " Damien Le Moal
2022-02-09 10:45 ` Damien Le Moal
2022-02-09 15:09 ` [Cluster-devel] " Christoph Hellwig
2022-02-09 15:09 ` Christoph Hellwig
2022-02-09 15:20 ` [Cluster-devel] " Andreas Gruenbacher
2022-02-09 15:20 ` Andreas Gruenbacher
2022-02-09 15:59 ` [Cluster-devel] " Lee Jones
2022-02-09 15:59 ` Lee Jones
2022-02-09 19:12 ` [Cluster-devel] " Matthew Wilcox
2022-02-09 19:12 ` Matthew Wilcox
2022-02-09 19:25 ` [Cluster-devel] " Lee Jones
2022-02-09 19:25 ` Lee Jones
2022-02-10 5:47 ` [Cluster-devel] " Christoph Hellwig
2022-02-10 5:47 ` Christoph Hellwig
2022-02-10 4:59 ` [Cluster-devel] " Darrick J. Wong
2022-02-10 4:59 ` Darrick J. Wong
2022-02-10 10:15 ` [Cluster-devel] " Lee Jones
2022-02-10 10:15 ` Lee Jones
2022-02-11 14:37 ` [Cluster-devel] " Matthew Wilcox
2022-02-11 14:37 ` Matthew Wilcox
2022-02-14 10:33 ` [Cluster-devel] " Lee Jones
2022-02-14 10:33 ` Lee Jones
2022-02-14 13:42 ` Christoph Hellwig [this message]
2022-02-14 13:42 ` Christoph Hellwig
2022-02-14 14:11 ` [Cluster-devel] " Lee Jones
2022-02-14 14:11 ` Lee Jones
2022-02-14 14:24 ` [Cluster-devel] " Matthew Wilcox
2022-02-14 14:24 ` Matthew Wilcox
2022-02-14 14:43 ` [Cluster-devel] " Lee Jones
2022-02-14 14:43 ` Lee Jones
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=20220214134206.GA29930@lst.de \
--to=hch@lst.de \
/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.