All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
	Mark Zhang <markzhang@nvidia.com>,
	Roland Dreier <rolandd@cisco.com>,
	Sean Hefty <sean.hefty@intel.com>
Subject: Re: [PATCH rdma-next v4 0/8] Fix memory corruption in CM
Date: Wed, 2 Jun 2021 16:00:35 -0300	[thread overview]
Message-ID: <20210602190035.GA140508@nvidia.com> (raw)
In-Reply-To: <cover.1622629024.git.leonro@nvidia.com>

On Wed, Jun 02, 2021 at 01:27:00PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Changelog:
> v4:
>  * Added comment near cm_destroy_av()
>  * Changed "unregistration lock" to be "mad_agent_lock" in the comment
>  * Removed unclear comment
> v3: https://lore.kernel.org/lkml/cover.1620720467.git.leonro@nvidia.com
>  * Removed double unlock
>  * Changes in cma_release flow
> v2: https://lore.kernel.org/lkml/cover.1619004798.git.leonro@nvidia.com
>  * Included Jason's patches in this series
> v1: https://lore.kernel.org/linux-rdma/20210411122152.59274-1-leon@kernel.org
>  * Squashed "remove mad_agent ..." patches to make sure that we don't
>    need to check for the NULL argument.
> v0: https://lore.kernel.org/lkml/20210318100309.670344-1-leon@kernel.org
> 
> -------------------------------------------------------------------------------
> 
> Hi,
> 
> This series from Mark fixes long standing bug in CM migration logic,
> reported by Ryan [1].
> 
> Thanks
> 
> [1] https://lore.kernel.org/linux-rdma/CAFMmRNx9cg--NUnZjFM8yWqFaEtsmAWV4EogKb3a0+hnjdtJFA@mail.gmail.com/
> 
> Jason Gunthorpe (4):
>   IB/cm: Pair cm_alloc_response_msg() with a cm_free_response_msg()
>   IB/cm: Split cm_alloc_msg()
>   IB/cm: Call the correct message free functions in cm_send_handler()
>   IB/cm: Tidy remaining cm_msg free paths
> 
> Mark Zhang (4):
>   Revert "IB/cm: Mark stale CM id's whenever the mad agent was
>     unregistered"
>   IB/cm: Simplify ib_cancel_mad() and ib_modify_mad() calls
>   IB/cm: Improve the calling of cm_init_av_for_lap and
>     cm_init_av_by_path
>   IB/cm: Protect cm_dev, cm_ports and mad_agent with kref and lock

Applied to for-next, thanks

Jason

      parent reply	other threads:[~2021-06-02 19:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 10:27 [PATCH rdma-next v4 0/8] Fix memory corruption in CM Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 1/8] IB/cm: Pair cm_alloc_response_msg() with a cm_free_response_msg() Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 2/8] IB/cm: Split cm_alloc_msg() Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 3/8] IB/cm: Call the correct message free functions in cm_send_handler() Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 4/8] IB/cm: Tidy remaining cm_msg free paths Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 5/8] Revert "IB/cm: Mark stale CM id's whenever the mad agent was unregistered" Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 6/8] IB/cm: Simplify ib_cancel_mad() and ib_modify_mad() calls Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 7/8] IB/cm: Improve the calling of cm_init_av_for_lap and cm_init_av_by_path Leon Romanovsky
2021-06-02 10:27 ` [PATCH rdma-next v4 8/8] IB/cm: Protect cm_dev, cm_ports and mad_agent with kref and lock Leon Romanovsky
2021-06-02 19:00 ` Jason Gunthorpe [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=20210602190035.GA140508@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=dledford@redhat.com \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=markzhang@nvidia.com \
    --cc=rolandd@cisco.com \
    --cc=sean.hefty@intel.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.