From: Milton Miller <miltonm@bga.com>
To: Martin Nyhus <martin.nyhus@gmx.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: [next] possible recursive locking in autofs4_write
Date: Sun, 15 Jan 2012 16:59:12 -0600 [thread overview]
Message-ID: <1326668352_245@mail4.comsite.net> (raw)
In-Reply-To: <201201152248.37439.martin.nyhus@gmx.com>
> Looks like mutex_lock should have been mutex_unlock in commit d668dc56
> (autofs4: deal with autofs4_write/autofs4_write races) at
> fs/autofs4/waitq.c:79, but I don't really know the code so if someone
> could have a look that would be great.
>
Yes, see http://lkml.indiana.edu/hypermail/linux/kernel/1201.1/02312.html
milton
prev parent reply other threads:[~2012-01-15 22:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 21:48 [next] possible recursive locking in autofs4_write Martin Nyhus
2012-01-15 22:59 ` Milton Miller [this message]
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=1326668352_245@mail4.comsite.net \
--to=miltonm@bga.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.nyhus@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.