All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anand Jain <Anand.Jain@oracle.com>
To: Rich Freeman <r-btrfs@thefreemanclan.net>
Cc: "G. Richard Bellamy" <rbellamy@pteradigm.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Upgrade to 3.19.2 Kernel fails to boot
Date: Wed, 01 Apr 2015 14:50:02 +0800	[thread overview]
Message-ID: <551B951A.2030606@oracle.com> (raw)
In-Reply-To: <CAGfcS_nc03H7ekvHBjZF7wEp2wFXuCXPA4Ar09mte4-+jOQKUA@mail.gmail.com>


Eric found something like this and has a fix with in the email.
Sub: "I think "btrfs: fix leak of path in btrfs_find_item" broke stable 
trees ..."

Anand

On 03/24/2015 06:40 PM, Rich Freeman wrote:
> On Tue, Mar 24, 2015 at 2:31 AM, Anand Jain <Anand.Jain@oracle.com> wrote:
>> Do you have this fix ..
>>
>>   [PATCH] Btrfs: release path before starting transaction in can_nocow_extent
>>
>> could you try ?.
>
> I believe I already have this patch.  3.18.9 contains this:
>
> commit bdeeab62a611f1f7cd48fd285ce568e8dcd0455a
> Merge: 797afdf 1bda19e
> Author: Linus Torvalds <torvalds@linux-foundation.org>
> Date:   Fri Oct 18 16:46:21 2013 -0700
>
>      Merge branch 'for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs
>
>      Pull btrfs fix from Chris Mason:
>       "Sage hit a deadlock with ceph on btrfs, and Josef tracked it down to a
>        regression in our initial rc1 pull.  When doing nocow writes we were
>        sometimes starting a transaction with locks held"
>
>      * 'for-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs:
>        Btrfs: release path before starting transaction in can_nocow_extent
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2015-04-01  6:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19 23:06 Upgrade to 3.19.2 Kernel fails to boot G. Richard Bellamy
2015-03-19 23:19 ` Chris Murphy
2015-03-22 21:15 ` Ochi
2015-03-22 21:25   ` Roman Mamedov
2015-03-23  8:23 ` Anand Jain
2015-03-23 13:22   ` Rich Freeman
2015-03-23 16:37     ` Rich Freeman
2015-03-24  6:31       ` Anand Jain
2015-03-24 10:40         ` Rich Freeman
2015-04-01  6:50           ` Anand Jain [this message]
2015-04-01 19:48             ` Rich Freeman
2015-03-31 21:24 ` Benjamin Hodgetts
2015-03-31 22:23   ` Chris Murphy

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=551B951A.2030606@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=r-btrfs@thefreemanclan.net \
    --cc=rbellamy@pteradigm.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.