From: Josef Bacik <josef@toxicpanda.com>
To: "Sebastian Döring" <moralapostel@gmail.com>,
dsterba@suse.cz, linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH][v3] btrfs: only search for left_info if there is no right_info
Date: Wed, 29 Jul 2020 11:43:40 -0400 [thread overview]
Message-ID: <e7370ce1-a799-3307-cfa3-f1a660d308c2@toxicpanda.com> (raw)
In-Reply-To: <CADkZQam9aJgNYy6bUXREYtS_fv1TLqyHbmkvs+aX9087AM62+g@mail.gmail.com>
On 7/29/20 11:42 AM, Sebastian Döring wrote:
> For reasons unrelated to btrfs I've been trying linux-next-20200728 today.
>
> This patch causes Kernel Oops and call trace (with
> try_merge_free_space on top of stack) on my system. Because of
> immediate system lock-up I can't provide a dmesg log and there's
> nothing in /var/log (probably because it immediately goes read-only),
> but removing this patch and rebuilding the kernel fixed my issues. I'm
> happy to help if you need more info in order to reproduce.
>
Lol I literally just hit this and sent the fixup to Dave when you posted this.
My bad, somehow it didn't hit either of us until just now. Thanks,
Josef
next prev parent reply other threads:[~2020-07-29 15:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 14:28 [PATCH][v3] btrfs: only search for left_info if there is no right_info Josef Bacik
2020-07-28 14:43 ` David Sterba
2020-07-29 15:42 ` Sebastian Döring
2020-07-29 15:43 ` Josef Bacik [this message]
2020-07-29 16:13 ` David Sterba
2020-07-30 11:42 ` Qu Wenruo
2020-07-30 14:02 ` Josef Bacik
2020-07-30 23:41 ` Qu Wenruo
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=e7370ce1-a799-3307-cfa3-f1a660d308c2@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=dsterba@suse.cz \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=moralapostel@gmail.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 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.