| To: | linux-kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock() |
| From: | Sami Farin <safari-xfs@xxxxxxxxxxxxx> |
| Date: | Mon, 8 Jan 2007 13:03:23 +0200 |
| In-reply-to: | <20070107213734.GS44411608@xxxxxxxxxxxxxxxxx> |
| Mail-followup-to: | linux-kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <20070104001420.GA32440@xxxxxxxxxxxxxxx> <20070107213734.GS44411608@xxxxxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.13 (2006-08-11) |
On Mon, Jan 08, 2007 at 08:37:34 +1100, David Chinner wrote: ... > > fstab was there just fine after -u. > > Oh, that still hasn't been fixed? Looked like it =) > Generic bug, not XFS - the global > semaphore->mutex cleanup converted the bd_mount_sem to a mutex, and > mutexes complain loudly when a the process unlocking the mutex is > not the process that locked it. > > Basically, the generic code is broken - the bd_mount_mutex needs to > be reverted back to a semaphore because it is locked and unlocked > by different processes. The following patch does this.... > > BTW, Sami, can you cc xfs@xxxxxxxxxxx on XFS bug reports in future; > you'll get more XFS savvy eyes there..... Forgot to. Thanks for patch. It fixed the issue, no more warnings. BTW. the fix is not in 2.6.git, either. -- Do what you love because life is too short for anything else. |
| Previous by Date: | Re: Review: fix block reservation to work with per-cpu counters, Christoph Hellwig |
|---|---|
| Next by Date: | kmem_alloc deadlock in SLES9 SP3, Heilige Gheist |
| Previous by Thread: | Re: xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock(), David Chinner |
| Next by Thread: | Re: xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock(), Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |