All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	linux-fsdevel@vger.kernel.org
Subject: Re: 2.6.35 causes deadlock when snapshotting root lv
Date: Thu, 17 Jun 2010 12:27:47 -0400	[thread overview]
Message-ID: <20100617162747.GA21336@redhat.com> (raw)
In-Reply-To: <4C1A4A74.9070105@cfl.rr.com>

On Thu, Jun 17 2010 at 12:16pm -0400,
Phillip Susi <psusi@cfl.rr.com> wrote:

> On 6/17/2010 10:27 AM, Mike Snitzer wrote:
> > Which filesystem are you using?  Which 2.6.35-rc?
> 
> ext4, rc1, 2, and 3.
> 
> > There haven't been _any_ changes to DM for 2.6.35 (some DM fixes may get
> > pushed to Linus once Alasdair gets back from traveling).
> 
> I just finished combing through the git log myself and was getting
> concerned that I couldn't find any dm changes.  At least now I know that
> I couldn't find them because they aren't there.
> 
> > So what this means is that the VFS (or ext4) freeze changes introduced
> > in 2.6.35 are the likely culprit:
> > 
> > http://git.kernel.org/linus/18e9e5104fcd9a9
> > http://git.kernel.org/linus/6b0310fbf087ad6
> 
> Yes, these do look suspicious.  I'll test reverting them tonight.

OK, I'd suggest reverting the VFS change (18e9e5104fcd9a9) first.

  reply	other threads:[~2010-06-17 16:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 13:50 2.6.35 causes deadlock when snapshotting root lv Phillip Susi
2010-06-17 14:27 ` Mike Snitzer
2010-06-17 16:16   ` Phillip Susi
2010-06-17 16:27     ` Mike Snitzer [this message]
2010-06-18  1:29       ` Phillip Susi
2010-06-18 18:55         ` Eric Sandeen
2010-06-18 19:19           ` Eric Sandeen
2010-06-18 19:23             ` Eric Sandeen
2010-06-23 19:37               ` [PATCH] ext4: fix freeze deadlock under IO Eric Sandeen
2010-08-01 21:41                 ` Ted Ts'o

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=20100617162747.GA21336@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=psusi@cfl.rr.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.