From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH] xen/xenbus: fix locking
Date: Thu, 5 Mar 2020 10:55:09 -0500 [thread overview]
Message-ID: <35457608-52a2-18b5-de09-95b5e465ea99@oracle.com> (raw)
In-Reply-To: <20200305100323.16736-1-jgross@suse.com>
On 3/5/20 5:03 AM, Juergen Gross wrote:
> Commit 060eabe8fbe726 ("xenbus/backend: Protect xenbus callback with
> lock") introduced a bug by holding a lock while calling a function
> which might schedule.
>
> Fix that by using a semaphore instead.
>
> Fixes: 060eabe8fbe726 ("xenbus/backend: Protect xenbus callback with lock")
> Signed-off-by: Juergen Gross <jgross@suse.com>
>
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
next prev parent reply other threads:[~2020-03-05 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 10:03 [PATCH] xen/xenbus: fix locking Juergen Gross
2020-03-05 15:55 ` Boris Ostrovsky [this message]
2020-03-06 11:14 ` Boris Ostrovsky
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=35457608-52a2-18b5-de09-95b5e465ea99@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).