From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, <david.vrabel@citrix.com>,
<boris.ostrovsky@oracle.com>, Juergen Gross <JGross@suse.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xenbus: don't BUG() on user mode induced condition
Date: Thu, 7 Jul 2016 12:21:07 +0100 [thread overview]
Message-ID: <577E3B23.4090102@citrix.com> (raw)
In-Reply-To: <577E1FAD02000078000FBD88@prv-mh.provo.novell.com>
On 07/07/16 08:23, Jan Beulich wrote:
> Inability to locate a user mode specified transaction ID should not
> lead to a kernel crash. For other than XS_TRANSACTION_START also
> don't issue anything to xenbus if the specified ID doesn't match that
> of any active transaction.
Applied to for-linus-4.7b and Cc'd to stable, thanks.
David
next prev parent reply other threads:[~2016-07-07 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 7:23 [PATCH] xenbus: don't BUG() on user mode induced condition Jan Beulich
2016-07-07 11:21 ` David Vrabel [this message]
2016-08-21 19:36 ` [Xen-devel] " Sylvain Munaut
2016-08-22 6:45 ` Jan Beulich
2016-08-22 7:21 ` Sylvain Munaut
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=577E3B23.4090102@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=JGross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.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