From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Morton <akpm@osdl.org>
Cc: David Chinner <dgc@sgi.com>,
linux-kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: bd_mount_mutex -> bd_mount_sem (was Re: xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock())
Date: Mon, 08 Jan 2007 21:12:40 -0600 [thread overview]
Message-ID: <45A30828.6000508@sandeen.net> (raw)
In-Reply-To: <20070108161917.73a4c2c6.akpm@osdl.org>
Andrew Morton wrote:
> On Tue, 9 Jan 2007 10:47:28 +1100
> David Chinner <dgc@sgi.com> wrote:
>
>> On Mon, Jan 08, 2007 at 10:40:54AM -0600, Eric Sandeen wrote:
>>> Sami Farin wrote:
>>>> 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 =)
>>> Hm, it was proposed upstream a while ago:
>>>
>>> http://lkml.org/lkml/2006/9/27/137
>>>
>>> I guess it got lost?
>> Seems like it. Andrew, did this ever get queued for merge?
>
> Seems not. I think people were hoping that various nasties in there
> would go away. We return to userspace with a kernel lock held??
Is a semaphore any worse than the current mutex in this respect? At
least unlocking from another thread doesn't violate semaphore rules. :)
-Eric
next prev parent reply other threads:[~2007-01-09 3:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 0:14 xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock() Sami Farin
2007-01-07 21:37 ` David Chinner
2007-01-08 11:03 ` Sami Farin
2007-01-08 16:40 ` Eric Sandeen
2007-01-08 23:47 ` bd_mount_mutex -> bd_mount_sem (was Re: xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock()) David Chinner
2007-01-09 0:19 ` Andrew Morton
2007-01-09 3:12 ` Eric Sandeen [this message]
2007-01-09 3:18 ` Andrew Morton
2007-01-09 3:38 ` Eric Sandeen
2007-01-09 3:51 ` Andrew Morton
2007-01-09 4:17 ` Nathan Scott
2007-01-09 4:49 ` David Chinner
2007-01-09 6:02 ` [**BULK SPAM**] " Nathan Scott
2007-01-09 10:04 ` Christoph Hellwig
2007-01-10 1:34 ` David Chinner
2007-01-09 10:02 ` Christoph Hellwig
2007-01-08 23:56 ` xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock() Andrew Morton
2007-01-09 6:41 ` Ingo Molnar
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=45A30828.6000508@sandeen.net \
--to=sandeen@sandeen.net \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox