From: Greg KH <gregkh@linuxfoundation.org>
To: Andrea Gelmini <andrea.gelmini@linux.it>
Cc: "Mike Snitzer" <snitzer@redhat.com>,
"Michael Laß" <bevan@bi-co.net>,
dm-devel@redhat.com, "Chris Murphy" <lists@colorremedies.com>,
"Qu Wenruo" <quwenruo.btrfs@gmx.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re: fstrim discarding too many or wrong blocks on Linux 5.1, leading to data loss
Date: Fri, 24 May 2019 17:10:51 +0200 [thread overview]
Message-ID: <20190524151051.GA28270@kroah.com> (raw)
In-Reply-To: <CAK-xaQZ9PCLgzFw0-YJ=Yvou=t0k=Vv-9JY4n3=VD2s=NaYL4w@mail.gmail.com>
On Fri, May 24, 2019 at 05:00:51PM +0200, Andrea Gelmini wrote:
> Hi Mike,
> I'm doing setup to replicate and test the condition. I see your
> patch is already in the 5.2 dev kernel.
> I'm going to try with latest git, and see what happens. Anyway,
> don't you this it would be good
> to have this patch ( 51b86f9a8d1c4bb4e3862ee4b4c5f46072f7520d )
> anyway in the 5.1 stable branch?
It's already in the 5.1 stable queue and will be in the next 5.1 release
in a day or so.
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-24 15:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 22:16 Massive filesystem corruption after balance + fstrim on Linux 5.1.2 Michael Laß
2019-05-16 23:41 ` Qu Wenruo
2019-05-16 23:42 ` Chris Murphy
2019-05-17 17:37 ` Michael Laß
2019-05-18 4:09 ` Chris Murphy
2019-05-18 9:18 ` Michael Laß
2019-05-18 9:31 ` Roman Mamedov
2019-05-18 10:09 ` Michael Laß
2019-05-18 10:26 ` Qu Wenruo
2019-05-19 19:55 ` fstrim discarding too many or wrong blocks on Linux 5.1, leading to data loss Michael Laß
2019-05-20 11:38 ` [dm-devel] " Michael Laß
2019-05-21 16:46 ` Michael Laß
2019-05-21 19:00 ` Andrea Gelmini
2019-05-21 19:59 ` Michael Laß
2019-05-21 20:12 ` Mike Snitzer
2019-05-24 15:00 ` Andrea Gelmini
2019-05-24 15:10 ` Greg KH [this message]
[not found] ` <CAK-xaQYPs62v971zm1McXw_FGzDmh_vpz3KLEbxzkmrsSgTfXw@mail.gmail.com>
2019-05-20 13:58 ` Michael Laß
2019-05-20 14:53 ` Andrea Gelmini
2019-05-20 16:45 ` Milan Broz
2019-05-20 19:58 ` Michael Laß
2019-05-21 18:54 ` Andrea Gelmini
2019-05-28 12:36 ` Massive filesystem corruption after balance + fstrim on Linux 5.1.2 Christoph Anton Mitterer
2019-05-28 12:43 ` Michael Laß
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=20190524151051.GA28270@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrea.gelmini@linux.it \
--cc=bevan@bi-co.net \
--cc=dm-devel@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=snitzer@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).