From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Adam Borowski <kilobyte@angband.pl>, Nick Terrell <terrelln@fb.com>
Cc: Kernel Team <Kernel-team@fb.com>, Chris Mason <clm@fb.com>,
Yann Collet <cyan@fb.com>, David Sterba <dsterba@suse.cz>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] btrfs: Add zstd support
Date: Mon, 10 Jul 2017 08:36:44 -0400 [thread overview]
Message-ID: <046c7611-be6d-ec4d-6489-e8f49a4453f6@gmail.com> (raw)
In-Reply-To: <20170708030706.tle2mpfe376jneft@angband.pl>
On 2017-07-07 23:07, Adam Borowski wrote:
> On Sat, Jul 08, 2017 at 01:40:18AM +0200, Adam Borowski wrote:
>> On Fri, Jul 07, 2017 at 11:17:49PM +0000, Nick Terrell wrote:
>>> On 7/6/17, 9:32 AM, "Adam Borowski" <kilobyte@angband.pl> wrote:
>>>> Got a reproducible crash on amd64:
>>
>>> Thanks for the bug report Adam! I'm looking into the failure, and haven't
>>> been able to reproduce it yet. I've built my kernel from your tree, and
>>> I ran your script with the kernel.tar tarball 100 times, but haven't gotten
>>> a failure yet.
>>
>>> I have a few questions to guide my debugging.
>>>
>>> - How many cores are you running with? I’ve run the script with 1, 2, and 4 cores.
>>> - Which version of gcc are you using to compile the kernel? I’m using gcc-6.2.0-5ubuntu12.
>>> - Are the failures always in exactly the same place, and does it fail 100%
>>> of the time or just regularly?
>>
>> 6 cores -- all on bare metal. gcc-7.1.0-9.
>> Lemme try with gcc-6, a different config or in a VM.
>
> I've tried the following:
> * gcc-6, defconfig (+btrfs obviously)
> * gcc-7, defconfig
> * gcc-6, my regular config
> * gcc-7, my regular config
> * gcc-7, debug + UBSAN + etc
> * gcc-7, defconfig, qemu-kvm with only 1 core
>
> Every build with gcc-7 reproduces the crash, every with gcc-6 does not.
>
Got a GCC7 tool-chain built, and I can confirm this here too, tested
with various numbers of cores ranging from 1-32 in a QEMU+KVM VM, with
various combinations of debug options and other config switches.
next prev parent reply other threads:[~2017-07-10 12:36 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 19:41 [PATCH v2 0/4] Add xxhash and zstd modules Nick Terrell
2017-06-29 19:41 ` [PATCH v2 1/4] lib: Add xxhash module Nick Terrell
2017-06-29 19:41 ` [PATCH v2 3/4] btrfs: Add zstd support Nick Terrell
2017-06-30 3:24 ` Adam Borowski
2017-06-30 12:16 ` E V
2017-06-30 14:21 ` David Sterba
2017-06-30 18:25 ` Austin S. Hemmelgarn
2017-06-30 23:01 ` Nick Terrell
2017-07-05 11:43 ` Austin S. Hemmelgarn
2017-07-05 18:18 ` Adam Borowski
2017-07-05 18:45 ` Austin S. Hemmelgarn
2017-07-05 19:35 ` Nick Terrell
2017-07-05 19:57 ` Austin S. Hemmelgarn
2017-07-06 0:25 ` Nick Terrell
2017-07-06 11:59 ` Austin S. Hemmelgarn
2017-07-06 12:09 ` Lionel Bouton
2017-07-06 12:27 ` Austin S. Hemmelgarn
2017-07-10 21:11 ` Clemens Eisserer
2017-07-06 16:32 ` Adam Borowski
2017-07-07 23:17 ` Nick Terrell
2017-07-07 23:40 ` Adam Borowski
2017-07-08 3:07 ` Adam Borowski
2017-07-10 12:36 ` Austin S. Hemmelgarn [this message]
2017-07-10 20:57 ` Nick Terrell
2017-07-11 4:57 ` Nick Terrell
2017-07-11 6:01 ` Nick Terrell
2017-07-12 3:38 ` Adam Borowski
2017-07-18 18:21 ` David Sterba
2017-06-29 19:41 ` [PATCH v2 4/4] squashfs: " Nick Terrell
2017-06-30 7:36 ` [PATCH v2 0/4] Add xxhash and zstd modules David Sterba
2017-06-30 16:46 ` Timofey Titovets
2017-06-30 19:52 ` Nick Terrell
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=046c7611-be6d-ec4d-6489-e8f49a4453f6@gmail.com \
--to=ahferroin7@gmail.com \
--cc=Kernel-team@fb.com \
--cc=clm@fb.com \
--cc=cyan@fb.com \
--cc=dsterba@suse.cz \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrelln@fb.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).