From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: "Nicholas A. Bellinger" <nab@linux-iscsi.org>,
linux-kernel@vger.kernel.org,
target-devel <target-devel@vger.kernel.org>
Subject: Re: [PATCH v3] target: close target_put_sess_cmd() vs. core_tmr_abort_task() race
Date: Mon, 18 Mar 2013 18:53:54 -0700 [thread overview]
Message-ID: <20130319015354.GA21045@kroah.com> (raw)
In-Reply-To: <20130318233413.GD9685@logfs.org>
On Mon, Mar 18, 2013 at 07:34:13PM -0400, Jörn Engel wrote:
> And because I'm lame and stupid, here's v3.
>
> It is possible for one thread to to take se_sess->sess_cmd_lock in
> core_tmr_abort_task() before taking a reference count on
> se_cmd->cmd_kref, while another thread in target_put_sess_cmd() drops
> se_cmd->cmd_kref before taking se_sess->sess_cmd_lock.
>
> This introduces kref_put_and_lock() and uses it in
> target_put_sess_cmd() to close the race window.
>
> Signed-off-by: Joern Engel <joern@logfs.org>
> ---
> drivers/target/target_core_transport.c | 17 +++++++++++------
> include/linux/kref.h | 26 ++++++++++++++++++++++++++
> 2 files changed, 37 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/target/target_core_transport.c b/drivers/target/target_core_transport.c
> index 04ec9cb..b98c158 100644
> --- a/drivers/target/target_core_transport.c
> +++ b/drivers/target/target_core_transport.c
> @@ -2207,21 +2207,19 @@ static void target_release_cmd_kref(struct kref *kref)
> {
> struct se_cmd *se_cmd = container_of(kref, struct se_cmd, cmd_kref);
> struct se_session *se_sess = se_cmd->se_sess;
> - unsigned long flags;
>
> - spin_lock_irqsave(&se_sess->sess_cmd_lock, flags);
> if (list_empty(&se_cmd->se_cmd_list)) {
> - spin_unlock_irqrestore(&se_sess->sess_cmd_lock, flags);
> + spin_unlock(&se_sess->sess_cmd_lock);
Wait, who has this locked? You took out the call to spin_lock_* above.
And why not _irqstore() anymore?
thanks,
greg k-h
next prev parent reply other threads:[~2013-03-19 1:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-18 22:28 [PATCH] target: close target_put_sess_cmd() vs. core_tmr_abort_task() race Jörn Engel
2013-03-19 0:04 ` Greg Kroah-Hartman
2013-03-18 22:56 ` Jörn Engel
2013-03-19 0:27 ` Greg Kroah-Hartman
2013-03-18 23:11 ` [PATCH v2] " Jörn Engel
2013-03-18 23:34 ` [PATCH v3] " Jörn Engel
2013-03-19 1:53 ` Greg Kroah-Hartman [this message]
2013-03-19 3:31 ` [PATCH v4] " Jörn Engel
2013-03-19 5:09 ` Greg Kroah-Hartman
2013-03-19 3:58 ` Jörn Engel
2013-03-19 13:38 ` Greg Kroah-Hartman
2013-03-19 15:03 ` Jörn Engel
2013-03-19 2:11 ` [PATCH v3] " Nicholas A. Bellinger
2013-03-19 2:39 ` Greg Kroah-Hartman
2013-03-19 2:46 ` Nicholas A. Bellinger
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=20130319015354.GA21045@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@vger.kernel.org \
/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