From: Chris Samuel <chris@csamuel.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: 3.11.5 kernel infinite loop
Date: Sat, 09 Nov 2013 12:22:19 +1100 [thread overview]
Message-ID: <5116277.EeSxDVfOuC@quad> (raw)
In-Reply-To: <pan$70f09$474e61ed$c27deec7$82b1529a@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On Wed, 6 Nov 2013 12:37:32 PM Duncan wrote:
> Note that there's another critical patch in-flight, patching a bug
> triggered by btrfs balance on filesystems with pre-allocated files (like
> systemd does with its journal and various torrent clients do with their
> downloads). But this one is currently being held up because stable rules
> require it to be in current mainline first, and 3.12 is out, but the two-
> week 3.13 commit window that would normally be open now is suspended for
> a week, as Linux is traveling without a reliable net connection. So the
> patch can't hit mainline, and thus won't hit stable unless an exception
> is made, until after Linus' vacation, when the commit window opens and
> the patch is accepted.
Greg K-H has said he'll accept stable patches that haven't hit the mainline
during this period.
cheers!
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 482 bytes --]
prev parent reply other threads:[~2013-11-09 1:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 1:52 3.11.5 kernel infinite loop Russell Coker
2013-11-06 12:37 ` Duncan
2013-11-09 1:22 ` Chris Samuel [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=5116277.EeSxDVfOuC@quad \
--to=chris@csamuel.org \
--cc=1i5t5.duncan@cox.net \
--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).