public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Ed Tomlinson <tomlins@CAM.ORG>,
	Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
	linux-kernel@vger.kernel.org
Subject: Re: mount hanging 2.4.12
Date: Sun, 14 Oct 2001 12:41:05 -0400	[thread overview]
Message-ID: <2169490000.1003077665@tiny> (raw)
In-Reply-To: <Pine.GSO.4.21.0110141231570.6026-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0110141231570.6026-100000@weyl.math.psu.edu>



On Sunday, October 14, 2001 12:32:33 PM -0400 Alexander Viro
<viro@math.psu.edu> wrote:

> 
> 
> On Sun, 14 Oct 2001, Chris Mason wrote:
> 
>> 
>> 
>> On Sunday, October 14, 2001 11:55:20 AM -0400 Ed Tomlinson
>> <tomlins@CAM.ORG> wrote:
>> > 
>> > Chris, what I suspect is happening is that the mount with the error
>> > leaves the sem locked.  After this any mount commant hangs - not just
>> > ones for the USB card read (ie. loop mount to build an initrd fails
>> > too..)
>> 
>> Yup, I see the, I'll send a new patch a little later today.
> 
> Cc: it to me, OK?

Sure, I was holding off on a cc to linux-kernel because I really don't like
it though ;-)  This is the LVM locking patch, so before making a snapshot
LVM wants to flush the FS and block new transactions.

LVM does this:
lockfs(dev) ;
make snapshot
unlockfs(dev) ;

This can happen while dev is either mounted or unmounted.  If dev was
unmounted when the lockfs was called, I'd like to make sure nobody can
mount it before the unlockfs is done.  I did this with a new semaphore in
fs/super.c, but I'd rather find something cleaner...

-chris


  reply	other threads:[~2001-10-14 16:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20011014034101.1955DB623@oscar.casa.dyndns.org>
2001-10-14  5:08 ` mount hanging 2.4.12 Alexander Viro
2001-10-14  5:26   ` IDE/SCSI Lockup syzygy
2001-10-14  5:46   ` mount hanging 2.4.12 Alexander Viro
2001-10-14 12:11     ` Ed Tomlinson
2001-10-14 13:48     ` Chris Mason
2001-10-14 14:23       ` Ed Tomlinson
2001-10-14 15:55       ` Ed Tomlinson
2001-10-14 16:30         ` Chris Mason
2001-10-14 16:32           ` Alexander Viro
2001-10-14 16:41             ` Chris Mason [this message]
2001-10-15  8:18             ` Chris Mason
2001-10-15 11:50               ` Ed Tomlinson
2001-10-15 15:37               ` Hans-Peter Jansen
2001-10-15 16:00                 ` Chris Mason
2001-10-14 16:30         ` Alexander Viro
2001-10-14  1:51 Ed Tomlinson
2001-10-14  2:02 ` Alexander Viro
2001-10-14  3:55   ` Brian Landsberger
2001-10-14  5:11     ` Alexander Viro
2001-10-14  8:09   ` Ookhoi
  -- strict thread matches above, loose matches on Subject: below --
2001-10-13 23:41 Ed Tomlinson
2001-10-13 23:55 ` Alexander Viro
2001-10-14  0:16   ` Riley Williams
2001-10-14  0:19     ` Alexander Viro
2001-10-14  2:01 ` Alexander Viro
2001-10-14  2:07   ` Ed Tomlinson
2001-10-14  2:36     ` Alexander Viro
2001-10-14  2:36   ` Matthew Dharm
2001-10-14  2:41     ` Ed Tomlinson
2001-10-14  3:25       ` Matthew Dharm

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=2169490000.1003077665@tiny \
    --to=mason@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdharm-kernel@one-eyed-alien.net \
    --cc=tomlins@CAM.ORG \
    --cc=viro@math.psu.edu \
    /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