linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: hard freezes with 3.9.0 during io-intensive loads
Date: Tue, 07 May 2013 23:16:03 +0200	[thread overview]
Message-ID: <ch7o5a-g0b.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: 51889A4D.8000201@jan-o-sch.net

Jan Schmidt <list.btrfs@jan-o-sch.net> schrieb:

>> I can reliably reproduce it from two different approaches. I'd like to
>> only apply the commits fixing it. Can you name them here?
> 
> In git log order:
> 
> 6ced2666 Btrfs: separate sequence numbers for delayed ref tracking and
> tree mod log ef9120b1 Btrfs: fix tree mod log regression on root split
> operations 2ed098ca Btrfs: fix accessing the root pointer in tree mod log
> functions 50723551 Btrfs: fix unlock after free on rewinded tree blocks
> 
> The commit ids are from josef's master branch
> (git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git) which
> is known not to be very stable regarding commit ids.

Thanks, applied almost cleanly to 3.9.0 vanilla with just one reject. And 
that was for some error message. I'm simply ignoring that and currently 
compiling it.

I will get back here with the result (fixed or not fixed for one or both 
situations).

Regards,
Kai


  reply	other threads:[~2013-05-07 21:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-05 10:25 hard freezes with 3.9.0 during io-intensive loads Kai Krakow
2013-05-05 16:10 ` Kai Krakow
2013-05-05 18:33   ` cwillu
2013-05-06  8:55   ` Jan Schmidt
2013-05-06  9:12     ` Harald Glatt
2013-05-06 20:29     ` Kai Krakow
2013-05-07  6:08       ` Jan Schmidt
2013-05-07 21:16         ` Kai Krakow [this message]
2013-05-08  0:24           ` Kai Krakow
2013-05-08 11:05             ` Jan Schmidt
2013-05-09 23:30               ` Kai Krakow
2013-05-10  7:01                 ` Jan Schmidt
2013-05-11 10:01                   ` Kai Krakow
2013-05-16  7:19                   ` Kai Krakow
2013-05-17 15:43                     ` Jan Schmidt
2013-05-06  0:39 ` Josef Bacik
2013-05-06  7:47   ` Kai Krakow

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=ch7o5a-g0b.ln1@hurikhan.ath.cx \
    --to=hurikhan77+btrfs@gmail.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).