All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dalessandro, Dennis" <dennis.dalessandro@intel.com>
To: "dledford@redhat.com" <dledford@redhat.com>,
	"pmladek@suse.com" <pmladek@suse.com>,
	"Hefty, Sean" <sean.hefty@intel.com>
Cc: "hal.rosenstock@gmail.com" <hal.rosenstock@gmail.com>,
	"tj@kernel.org" <tj@kernel.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] IB/rdmavt: cq ktrhead worker fix and API update
Date: Thu, 20 Oct 2016 12:56:27 +0000	[thread overview]
Message-ID: <1476968182.23693.14.camel@intel.com> (raw)
In-Reply-To: <1476878840-14548-1-git-send-email-pmladek@suse.com>

On Wed, 2016-10-19 at 14:07 +0200, Petr Mladek wrote:
> The kthread worker API has been improved in 4.9-rc1. The 2nd
> patch uses the new functions and simplifies the kthread worker
> creation and destroying.
> 
> I have found a possible race when working on the API conversion.
> A proposed fix is in the 1st patch.
> 
> Both changes are compile tested only. I did not find an easy way
> how to test them at runtime.
> 
> Petr Mladek (2):
>   IB/rdmavt: Avoid queuing work into a destroyed cq kthread worker
>   IB/rdmavt: Handle the kthread worker using the new API
> 
>  drivers/infiniband/sw/rdmavt/cq.c | 64 +++++++++++++++++----------
> ------------
>  1 file changed, 27 insertions(+), 37 deletions(-)

Thanks for the patches. I'm going to take a closer look, I just now
seen these.

-Denny

  parent reply	other threads:[~2016-10-20 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 12:07 [PATCH 0/2] IB/rdmavt: cq ktrhead worker fix and API update Petr Mladek
2016-10-19 12:07 ` [PATCH 1/2] IB/rdmavt: Avoid queuing work into a destroyed cq kthread worker Petr Mladek
2016-10-19 12:07 ` [PATCH 2/2] IB/rdmavt: Handle the kthread worker using the new API Petr Mladek
2016-10-20 12:56 ` Dalessandro, Dennis [this message]
2016-12-14 17:17   ` [PATCH 0/2] IB/rdmavt: cq ktrhead worker fix and API update Doug Ledford

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=1476968182.23693.14.camel@intel.com \
    --to=dennis.dalessandro@intel.com \
    --cc=dledford@redhat.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=sean.hefty@intel.com \
    --cc=tj@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.