From: Adam Borowski <kilobyte@angband.pl>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: splat in split_leaf with integrity checking
Date: Tue, 20 Sep 2016 23:44:36 +0200 [thread overview]
Message-ID: <20160920214436.GA14662@angband.pl> (raw)
In-Reply-To: <20160920022146.GB28802@localhost.localdomain>
On Mon, Sep 19, 2016 at 07:21:47PM -0700, Liu Bo wrote:
> On Tue, Sep 20, 2016 at 03:39:27AM +0200, Adam Borowski wrote:
> > Hi!
> > I just had the following splat in 4.8-rc6 for the third time in a week:
>
> Sorry for the trouble, this is caused by my patch and here are two fixes[1]
> to get it right with integrity check (not sure if they've been queued yet).
>
> Here is a discussion that explains why we remove it[2].
>
> [1] https://patchwork.kernel.org/patch/9320077/
> https://patchwork.kernel.org/patch/9311541/
>
> [2] http://www.spinics.net/lists/linux-btrfs/msg58506.html
Thanks! I should have noticed these posts and not bother you; anyway, I've
applied the patches and stress-tested during the day, just in case they
break something. All seems to work fine now -- and as I had a splat just
after posting this when copying that big file, and another during the kernel
compile, the bug would likely have triggered by now.
Meow!
--
Second "wet cat laying down on a powered-on box-less SoC on the desk" close
shave in a week. Protect your ARMs, folks!
prev parent reply other threads:[~2016-09-20 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 1:39 splat in split_leaf with integrity checking Adam Borowski
2016-09-20 2:21 ` Liu Bo
2016-09-20 21:44 ` Adam Borowski [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=20160920214436.GA14662@angband.pl \
--to=kilobyte@angband.pl \
--cc=bo.li.liu@oracle.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 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).