linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Dave Chinner <david@fromorbit.com>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] loop: Make explicit loop device destruction lazy
Date: Fri, 28 Sep 2012 10:38:44 -0400	[thread overview]
Message-ID: <20120928143844.GA1454@redhat.com> (raw)
In-Reply-To: <506562CE.2070500@kernel.dk>

On Fri, Sep 28, 2012 at 10:41:50AM +0200, Jens Axboe wrote:

 > > Turns out that blkid is running simultaneously with losetup -d, and
 > > so it sees an elevated reference count and returns EBUSY.  But why
 > > is blkid running? It's obvious, isn't it? udev has decided to try
 > > and find out what is on the block device as a result of a creation
 > > notification. And it is racing with mkfs, so might still be scanning
 > > the device when mkfs finishes and we try to tear it down.
 > > 
 > I hear that %^#@#! blkid behavior, it is such a pain in the neck. I
 > don't know how many times I've had to explain that behaviour to people
 > who run write testing with tracing, wonder wtf there are reads in the
 > trace.
 
Could this problem explain this bug too ? https://bugzilla.redhat.com/show_bug.cgi?id=853674

	Dave

  reply	other threads:[~2012-09-28 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-28  6:09 [PATCH] loop: Make explicit loop device destruction lazy Dave Chinner
2012-09-28  8:41 ` Jens Axboe
2012-09-28 14:38   ` Dave Jones [this message]
2012-09-29  5:51     ` Jens Axboe
2012-09-28 15:02   ` Jeff Moyer
2012-09-29  5:50     ` Jens Axboe
2012-10-01 14:00       ` Jeff Moyer

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=20120928143844.GA1454@redhat.com \
    --to=davej@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).