All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: efremov@linux.com, saeedm@mellanox.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] net/mlx5: DR, Fix freeing in dr_create_rc_qp()" failed to apply to 5.7-stable tree
Date: Mon, 22 Jun 2020 20:42:07 -0400	[thread overview]
Message-ID: <20200623004207.GR1931@sasha-vm> (raw)
In-Reply-To: <1592574342143235@kroah.com>

On Fri, Jun 19, 2020 at 03:45:42PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.7-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 47a357de2b6b706af3c9471d5042f9ba8907031e Mon Sep 17 00:00:00 2001
>From: Denis Efremov <efremov@linux.com>
>Date: Mon, 1 Jun 2020 19:45:26 +0300
>Subject: [PATCH] net/mlx5: DR, Fix freeing in dr_create_rc_qp()
>
>Variable "in" in dr_create_rc_qp() is allocated with kvzalloc() and
>should be freed with kvfree().
>
>Fixes: 297cccebdc5a ("net/mlx5: DR, Expose an internal API to issue RDMA operations")
>Cc: stable@vger.kernel.org
>Signed-off-by: Denis Efremov <efremov@linux.com>
>Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>

Conflict due to quite a lot of refactoring around QP. I've fixed it up
and queued for 5.7 and 5.4.

-- 
Thanks,
Sasha

      reply	other threads:[~2020-06-23  0:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 13:45 FAILED: patch "[PATCH] net/mlx5: DR, Fix freeing in dr_create_rc_qp()" failed to apply to 5.7-stable tree gregkh
2020-06-23  0:42 ` Sasha Levin [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=20200623004207.GR1931@sasha-vm \
    --to=sashal@kernel.org \
    --cc=efremov@linux.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=saeedm@mellanox.com \
    --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 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.