From: Greg KH <greg@kroah.com>
To: Filipe Manana <fdmanana@gmail.com>
Cc: "Gerald Hopf" <gerald.hopf@nv-systems.net>,
"Михаил Гаврилов" <mikhail.v.gavrilov@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs]
Date: Wed, 9 Dec 2015 19:48:02 -0500 [thread overview]
Message-ID: <20151210004802.GA22241@kroah.com> (raw)
In-Reply-To: <CAL3q7H5354BV39V36zg60ENrALqDeiqDnoRCvhP2SuBjYeuoSg@mail.gmail.com>
On Wed, Dec 09, 2015 at 11:29:48PM +0000, Filipe Manana wrote:
> On Wed, Dec 9, 2015 at 11:05 PM, Gerald Hopf <gerald.hopf@nv-systems.net> wrote:
> >
> >>> kernel BUG at fs/btrfs/extent-tree.c:1833!
> >>
> >> We got this fixed in 4.4-rc1:
> >>
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=2c3cf7d5f6105bb957df125dfce61d4483b8742d
> >>
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b06c4bf5c874a57254b197f53ddf588e7a24a2bf
> >>
> >> Patches were tagged for stable releases but weren't yet backported to
> >> 4.2 and 4.3 (the issue affects all 4.2 and 4.3 releases at the
> >> moment).
> >>
> >> cheers
> >
> > Could someone please backport this important fix and merge it into the
> > stable kernels?
> > Today Kernel 4.2.7 and 4.3.1 were finally released and as far as I can see
> > in the changelog no btrfs fixes were included in these updates.
> > => still can't do balance without crashing the system
>
> It's up to the stable team (cc'ed) to do that. For some reason, all
> patches (at least btrfs ones) tagged for stable haven't been added to
> 4.3.x and 4.2.x at least for quite some time. Probably just a long
> queue and a busy maintainer or on vacations or something like that.
Yes a combination of those two things. I'm digging myself out of the
stable queue, right now there are over 10 btrfs stable patches in the
queue that I haven't even touched yet, sorry.
thanks,
greg k-h
prev parent reply other threads:[~2015-12-10 0:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABXGCsMgw7NH5VzPvOVKrkd03CH7Dmjhg1xizwhknLDg9Vk2AA@mail.gmail.com>
[not found] ` <CAL3q7H5kiPdR0N2k=q92MFS-gcCE4A==yB2TLBgze43haARvaQ@mail.gmail.com>
[not found] ` <5668B3BE.60500@nv-systems.net>
2015-12-09 23:29 ` kernel BUG at fs/btrfs/extent-tree.c:1833! [btrfs] Filipe Manana
2015-12-10 0:48 ` Greg KH [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=20151210004802.GA22241@kroah.com \
--to=greg@kroah.com \
--cc=fdmanana@gmail.com \
--cc=gerald.hopf@nv-systems.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=stable@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).