From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: david.vrabel@citrix.com, roger.pau@citrix.com,
xen-devel <xen-devel@lists.xen.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] xen/blkback: Check for insane amounts of request on the ring.
Date: Fri, 7 Jun 2013 08:41:02 -0700 (PDT) [thread overview]
Message-ID: <20130607154102.GB24882@phenom.dumpdata.com> (raw)
In-Reply-To: <51B092F702000078000DBDA8@nat28.tlf.novell.com>
On Thu, Jun 06, 2013 at 12:47:35PM +0100, Jan Beulich wrote:
> >>> On 05.06.13 at 19:35, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > @@ -230,6 +231,7 @@ static int xen_blkif_map(struct xen_blkif *blkif, unsigned long shared_page,
> > static void xen_blkif_disconnect(struct xen_blkif *blkif)
> > {
> > if (blkif->xenblkd) {
> > + wake_up(&blkif->shutdown_wq);
> > kthread_stop(blkif->xenblkd);
> > blkif->xenblkd = NULL;
> > }
>
> Btw., wouldn't the wake_up() better be done after the kthread_stop(),
> so that when the corresponding wait_event_interruptible() checks
> whether to exit the terminating kthread_should_stop() is guaranteed
> to evaluate to true (otherwise I think there's potential for it to never
> exit)?
I think you are right. I did the change and the tests were OK.
>
> Jan
>
next prev parent reply other threads:[~2013-06-07 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 19:57 [PATCH] xen/blkback: Check for insane amounts of request on the ring Konrad Rzeszutek Wilk
2013-06-05 15:50 ` Jan Beulich
2013-06-05 17:35 ` Konrad Rzeszutek Wilk
2013-06-06 6:28 ` Jan Beulich
2013-06-06 11:47 ` Jan Beulich
2013-06-07 15:41 ` Konrad Rzeszutek Wilk [this message]
2013-06-07 20:11 ` Konrad Rzeszutek Wilk
2013-06-10 15:52 ` Jan Beulich
2013-06-10 16:43 ` Konrad Rzeszutek Wilk
2013-06-11 7:42 ` Jan Beulich
2013-06-11 13:17 ` konrad wilk
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=20130607154102.GB24882@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xen.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