From: Roland Dreier <rdreier@cisco•com>
To: Stefan Roscher <ossrosch@linux•vnet.ibm.com>
Cc: LinuxPPC-Dev <linuxppc-dev@ozlabs•org>,
fenkes@de•ibm.com, LKML <linux-kernel@vger•kernel.org>,
raisch@de•ibm.com, OF-EWG <ewg@lists•openfabrics.org>
Subject: Re: [ewg] [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled.
Date: Wed, 07 May 2008 11:02:40 -0700 [thread overview]
Message-ID: <adar6ceuh4v.fsf@cisco.com> (raw)
In-Reply-To: <200805071800.15595.ossrosch@linux.vnet.ibm.com> (Stefan Roscher's message of "Wed, 7 May 2008 18:00:14 +0200")
> I agree, that's why I posted the driver fix first.
Glad we agree :)
I thought about it a little more and really convinced myself that there
is no good way for generic code to handle this race.
> So, will you apply it next?
Yes, will apply it shortly.
- R.
next prev parent reply other threads:[~2008-05-07 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 11:19 [PATCH] IB/ehca: Protect QP against destroying until all async events for it are handled Stefan Roscher
2008-05-07 15:32 ` [ewg] " Roland Dreier
2008-05-07 16:00 ` Stefan Roscher
2008-05-07 18:02 ` Roland Dreier [this message]
2008-05-07 19:18 ` Roland Dreier
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=adar6ceuh4v.fsf@cisco.com \
--to=rdreier@cisco$(echo .)com \
--cc=ewg@lists$(echo .)openfabrics.org \
--cc=fenkes@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=ossrosch@linux$(echo .)vnet.ibm.com \
--cc=raisch@de$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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