From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: linux-btrfs@vger.kernel.org
Cc: Chris Mason <clm@fb.com>
Subject: Re: btrfs rare silent data corruption with kernel data leak (updated with some bisection results)
Date: Sun, 9 Oct 2016 00:11:22 -0400 [thread overview]
Message-ID: <20161009041122.GV21290@hungrycats.org> (raw)
In-Reply-To: <20161008070200.GU21290@hungrycats.org>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Sat, Oct 08, 2016 at 03:02:00AM -0400, Zygo Blaxell wrote:
> On Sat, Oct 08, 2016 at 02:10:08AM -0400, Zygo Blaxell wrote:
> [...]
> > The "write half" of the bug seems to appear first somewhere between v3.8
> > and v3.9. I have not been able to reproduce it with v3.8.13, v3.7.10, or
> > v3.6.11. I can reproduce it in v3.9.11, v3.12.64, and v3.18.13..v4.7.5.
>
> After six more iterations of the 'repro' script, I can reproduce "write
> half" on 3.8.13.
>
> Bisection is hard. Bisecting ancient bugs even more so.
I increased the number of iterations of the 'repro' script to 100,
although in practice no more than 20 are required. With this test
case, I can find the bug in kernels as early as v3.5.7. v3.0..v3.4 crash
before they complete one run of the 'repro' script. Earlier kernels
don't work with the userspace on my testing machine, and going back more
than four years is not worth the effort IMHO.
At the other end of the timeline, I also reproduced this bug on 4.8.1.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-10-09 4:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 4:55 btrfs rare silent data corruption with kernel data leak Zygo Blaxell
2016-09-21 11:14 ` Paul Jones
2016-09-21 13:02 ` Zygo Blaxell
2016-09-22 17:49 ` Kai Krakow
2016-09-22 19:35 ` Christoph Anton Mitterer
2016-09-22 20:42 ` Chris Mason
2016-09-24 2:28 ` Zygo Blaxell
2016-09-28 16:18 ` [PATCH][RFC] btrfs rare silent data corruption with kernel data leak (updated, preliminary patch) Zygo Blaxell
2016-10-08 6:10 ` btrfs rare silent data corruption with kernel data leak (updated with some bisection results) Zygo Blaxell
2016-10-08 7:02 ` Zygo Blaxell
2016-10-09 4:11 ` Zygo Blaxell [this message]
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=20161009041122.GV21290@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.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.