From: Nicolai Stange <nicstange@gmail.com>
To: Nicolai Stange <nicstange@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] debugfs: fix double unlock in open_proxy_open()
Date: Sat, 12 Mar 2016 16:20:31 +0100 [thread overview]
Message-ID: <87pouzafk0.fsf@gmail.com> (raw)
In-Reply-To: <1457795345-23014-1-git-send-email-nicstange@gmail.com> (Nicolai Stange's message of "Sat, 12 Mar 2016 16:09:05 +0100")
Nicolai Stange <nicstange@gmail.com> writes:
> In case an open is racing with a debugfs file removal, the corresponding
> error path in open_proxy_open() releases its SRCU read side critical
> section twice, i.e. it does a double unlock.
This one has been reported by Rasmus Villemoes:
http://lkml.kernel.org/g/87d1r2uh95.fsf@rasmusvillemoes.dk
Thank you very much!
Nicolai
next prev parent reply other threads:[~2016-03-12 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 15:09 [PATCH] debugfs: fix double unlock in open_proxy_open() Nicolai Stange
2016-03-12 15:20 ` Nicolai Stange [this message]
2016-03-12 15:22 ` Nicolai Stange
2016-03-22 13:15 ` Nicolai Stange
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=87pouzafk0.fsf@gmail.com \
--to=nicstange@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
/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