From: Christoph Hellwig <hch@infradead.org>
To: dsterba@suse.cz, Linus Torvalds <torvalds@linux-foundation.org>,
David Sterba <dsterba@suse.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] Btrfs updates for 5.8, part 2
Date: Mon, 15 Jun 2020 06:26:32 -0700 [thread overview]
Message-ID: <20200615132632.GA27848@infradead.org> (raw)
In-Reply-To: <20200615125701.GY27795@twin.jikos.cz>
On Mon, Jun 15, 2020 at 02:57:01PM +0200, David Sterba wrote:
> On Sun, Jun 14, 2020 at 09:50:17AM -0700, Linus Torvalds wrote:
> > On Sun, Jun 14, 2020 at 4:56 AM David Sterba <dsterba@suse.com> wrote:
> > >
> > > Reverts are not great, but under current circumstances I don't see
> > > better options.
> >
> > Pulled. Are people discussing how to make iomap work for everybody?
> > It's a bit sad if we can't have the major filesystems move away from
> > the old buffer head interfaces to a common more modern one..
>
> Yes, it's fixable and we definitely want to move to iomap. The direct to
> buffered fallback would fix one of the problems, but this would also
> mean that xfs would start doing that. Such change should be treated more
> like a feature development than a bugfix, imposed by another filesystem,
> and xfs people rightfully complained.
We can trivially key that off a flag at least for 5.8. I suspect the
fallback actually is the right thing for XFS in the long run for that
particular case.
next prev parent reply other threads:[~2020-06-15 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 11:56 [GIT PULL] Btrfs updates for 5.8, part 2 David Sterba
2020-06-14 16:50 ` Linus Torvalds
2020-06-15 11:46 ` Christoph Hellwig
2020-06-15 12:57 ` David Sterba
2020-06-15 13:26 ` Christoph Hellwig [this message]
2020-06-15 13:40 ` Filipe Manana
2020-06-14 18:55 ` 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=20200615132632.GA27848@infradead.org \
--to=hch@infradead.org \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox