| To: | Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|---|---|
| Subject: | [xfs-masters] Re: xfs_io "BUG: lock held when returning to user space!" on suspend |
| From: | David Chinner <dgc@xxxxxxx> |
| Date: | Thu, 3 Apr 2008 07:57:20 +1000 |
| Cc: | David Chinner <dgc@xxxxxxx>, xfs-masters@xxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx> |
| In-reply-to: | <47F3D76E.1070400@xxxxxxxx> |
| References: | <47F3D76E.1070400@xxxxxxxx> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.2.1i |
On Wed, Apr 02, 2008 at 11:58:54AM -0700, Jeremy Fitzhardinge wrote:
> I'm getting this:
>
> ================================================
> [ BUG: lock held when returning to user space! ]
> ------------------------------------------------
> xfs_io/18796 is leaving the kernel with locks still held!
> 1 lock held by xfs_io/18796:
> #0: (&type->s_umount_key#19){----}, at: [<c048c9ac>] get_super+0x42/0x87
>
> when I suspend, possibly during an xfs-freeze. There don't seem to be any
> ill-effects.
Yup, both the sb->s_umount and bdev->bd_mount_sem seaphores are held
across freeze_bdev()/thaw_bdev(), and they are issued via separate
ioctls generally from separate processes. Not great design, but not
a bug....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [xfs-masters] xfs_io "BUG: lock held when returning to user space!" on suspend, Jeremy Fitzhardinge |
|---|---|
| Next by Date: | [xfs-masters] Re: xfs_io "BUG: lock held when returning to user space!" on suspend, Peter Zijlstra |
| Previous by Thread: | [xfs-masters] xfs_io "BUG: lock held when returning to user space!" on suspend, Jeremy Fitzhardinge |
| Next by Thread: | [xfs-masters] Re: xfs_io "BUG: lock held when returning to user space!" on suspend, Peter Zijlstra |
| Indexes: | [Date] [Thread] [Top] [All Lists] |