From: Jiri Slaby <jslaby@suse.cz>
To: gregkh@linuxfoundation.org, sagig@mellanox.com,
jennyf@mellanox.com, nab@linux-iscsi.org
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "iser-target: Fix possible use-after-free" has been added to the 3.14-stable tree
Date: Tue, 23 Jun 2015 15:24:05 +0200 [thread overview]
Message-ID: <55895DF5.9020709@suse.cz> (raw)
In-Reply-To: <143502972110499@kroah.com>
On 06/23/2015, 05:22 AM, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> iser-target: Fix possible use-after-free
>
> to the 3.14-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> iser-target-fix-possible-use-after-free.patch
> and it can be found in the queue-3.14 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
>
>
> From 524630d5824c7a75aab568c6bd1423fd748cd3bb Mon Sep 17 00:00:00 2001
> From: Sagi Grimberg <sagig@mellanox.com>
> Date: Thu, 4 Jun 2015 19:49:21 +0300
> Subject: iser-target: Fix possible use-after-free
>
> From: Sagi Grimberg <sagig@mellanox.com>
>
> commit 524630d5824c7a75aab568c6bd1423fd748cd3bb upstream.
...
> --- a/drivers/infiniband/ulp/isert/ib_isert.c
> +++ b/drivers/infiniband/ulp/isert/ib_isert.c
> @@ -2952,6 +2952,7 @@ static void isert_free_conn(struct iscsi
> {
> struct isert_conn *isert_conn = conn->context;
>
> + isert_wait4flush(isert_conn);
This breaks build in 3.12, and I think 3.14 and 3.10 is affected too. We
do not have isert_wait4flush yet.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2015-06-23 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 3:22 Patch "iser-target: Fix possible use-after-free" has been added to the 3.14-stable tree gregkh
2015-06-23 13:24 ` Jiri Slaby [this message]
2015-06-24 14:49 ` Greg KH
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=55895DF5.9020709@suse.cz \
--to=jslaby@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jennyf@mellanox.com \
--cc=nab@linux-iscsi.org \
--cc=sagig@mellanox.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@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