From: Ismael Luceno <ismael@iodev.co.uk>
To: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [v4] btrfs: add missing memset while reading compressed inline extents
Date: Thu, 30 Mar 2017 12:46:40 -0300 [thread overview]
Message-ID: <20170330154639.GB21626@pirotess.Home> (raw)
In-Reply-To: <1489182344-29818-1-git-send-email-ce3g8jdj@umail.furryterror.org>
On 10/Mar/2017 16:45, Zygo Blaxell wrote:
> This is a story about 4 distinct (and very old) btrfs bugs.
>
<...>
Tested-by: Ismael Luceno <ismael@iodev.co.uk>
I encountered the issue in the wild; it caused frequent segfaults
at ld.so after some hours of operation, as well as integrity check
failures. A quick inspection revealed corruption in the ELF headers,
with garbage where there should be zeros.
I managed to reproduce the issue right away by enabling page poisoning,
and the problem effectively goes away when applying the patch.
prev parent reply other threads:[~2017-03-30 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 21:45 [PATCH v4] btrfs: add missing memset while reading compressed inline extents Zygo Blaxell
2017-03-30 15:46 ` Ismael Luceno [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=20170330154639.GB21626@pirotess.Home \
--to=ismael@iodev.co.uk \
--cc=ce3g8jdj@umail.furryterror.org \
--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 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).