From: Dave Chinner <david@fromorbit.com>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: ansgar.loesser@kom.tu-darmstadt.de,
"Darrick J. Wong" <djwong@kernel.org>,
"Josef Bacik" <josef@toxicpanda.com>,
"Christoph Hellwig" <hch@lst.de>,
"Amir Goldstein" <amir73il@gmail.com>,
"Mark Fasheh" <mark@fasheh.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Miklos Szeredi" <mszeredi@redhat.com>,
"Al Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Security Officers" <security@kernel.org>,
"Max Schlecht" <max.schlecht@informatik.hu-berlin.de>,
"Björn Scheuermann" <scheuermann@kom.tu-darmstadt.de>
Subject: Re: [PATCH] vf/remap: return the amount of bytes actually deduplicated
Date: Fri, 15 Jul 2022 09:15:18 +1000 [thread overview]
Message-ID: <20220714231518.GI3600936@dread.disaster.area> (raw)
In-Reply-To: <CAHk-=wh1TEGEAhj-obgjhMzDNaSxipZsdAUNS6dApt=OxktZAQ@mail.gmail.com>
On Thu, Jul 14, 2022 at 03:42:13PM -0700, Linus Torvalds wrote:
> On Thu, Jul 14, 2022 at 3:32 PM Dave Chinner <david@fromorbit.com> wrote:
> >
> > Linus, can you please revert this commit for the 5.19 series (before
> > the stable autosel bot sends it back to stable kernels, please!) to
> > give us more time to investigate and consider the impact of the the
> > API change on userspace applications before we commit to changing
> > the API.
>
> Done.
Thanks!
> That said, even from the fastest output, I have to say that the new
> behavior looks like the right one, and the old one just returned a
> fantasy that didn't actually match what the dedupe operation actually
> *did*.
Very true, and I'm definitely not arguing that the change is wrong.
We just need a bit of time to look at the various major dedupe apps
and check that they still do the right thing w.r.t. proposed change.
This late in the cycle I want to make sure we don't end up screwing
things up and creating unnecessary urgent work for anyone in the
near future...
> But leaving this for later is not a problem.
*nod*
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-07-14 23:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 12:11 Information Leak: FIDEDUPERANGE ioctl allows reading writeonly files Ansgar Lößer
2022-07-12 17:33 ` Linus Torvalds
2022-07-12 18:43 ` Matthew Wilcox
2022-07-12 18:47 ` Linus Torvalds
2022-07-12 18:51 ` Linus Torvalds
2022-07-12 19:02 ` Josef Bacik
2022-07-12 19:07 ` Linus Torvalds
2022-07-12 19:23 ` Linus Torvalds
2022-07-12 20:03 ` Josef Bacik
2022-07-12 20:48 ` Linus Torvalds
2022-07-13 0:48 ` Darrick J. Wong
2022-07-13 2:58 ` Linus Torvalds
2022-07-13 4:14 ` Linus Torvalds
2022-07-13 6:46 ` Dave Chinner
2022-07-13 7:49 ` [PATCH] fs/remap: constrain dedupe of EOF blocks Dave Chinner
2022-07-13 8:19 ` Linus Torvalds
2022-07-13 17:18 ` Ansgar Lößer
2022-07-13 17:26 ` Linus Torvalds
2022-07-13 18:51 ` [PATCH] vf/remap: return the amount of bytes actually deduplicated Ansgar Lößer
2022-07-13 19:09 ` Linus Torvalds
2022-07-14 0:22 ` Dave Chinner
2022-07-14 1:03 ` Linus Torvalds
2022-07-16 21:15 ` Mark Fasheh
2022-07-14 22:32 ` Dave Chinner
2022-07-14 22:42 ` Linus Torvalds
2022-07-14 23:15 ` Dave Chinner [this message]
2022-07-13 8:16 ` Information Leak: FIDEDUPERANGE ioctl allows reading writeonly files Linus Torvalds
2022-07-13 23:48 ` Dave Chinner
2022-07-13 17:17 ` Ansgar Lößer
2022-07-13 17:16 ` Ansgar Lößer
2022-07-13 22:43 ` Dave Chinner
2022-07-13 17:14 ` Ansgar Lößer
2022-07-13 18:03 ` Linus Torvalds
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=20220714231518.GI3600936@dread.disaster.area \
--to=david@fromorbit.com \
--cc=amir73il@gmail.com \
--cc=ansgar.loesser@kom.tu-darmstadt.de \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=max.schlecht@informatik.hu-berlin.de \
--cc=mszeredi@redhat.com \
--cc=scheuermann@kom.tu-darmstadt.de \
--cc=security@kernel.org \
--cc=torvalds@linuxfoundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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.