From: Greg KH <gregkh@linuxfoundation.org>
To: "M. Vefa Bicakci" <m.v.b@runbox.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: A xenbus bug-fix commit missing on the stable/linux-4.4.y branch
Date: Thu, 27 Oct 2016 18:17:56 +0200 [thread overview]
Message-ID: <20161027161756.GA15284@kroah.com> (raw)
In-Reply-To: <d9b12ab9-2e52-a24e-3b52-d97a7b5414e1@runbox.com>
On Thu, Oct 27, 2016 at 06:34:18PM +0300, M. Vefa Bicakci wrote:
> Dear all,
>
> I recently found out that the following commit is not on the linux-4.4.y branch, even though it is on the linux-4.7.y and linux-4.8.y branches:
>
> === 8< ===
> commit 9a035a40f7f3f6708b79224b86c5777a3334f7ea
> Author: Jan Beulich <JBeulich@suse.com>
> Date: Mon Aug 15 09:02:38 2016 -0600
>
> xenbus: don't look up transaction IDs for ordinary writes
>
> This should really only be done for XS_TRANSACTION_END messages, or
> else at least some of the xenstore-* tools don't work anymore.
>
> Fixes: 0beef634b8 ("xenbus: don't BUG() on user mode induced condition")
> Reported-by: Richard Sch�tz <rschuetz@uni-koblenz.de>
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Tested-by: Richard Sch�tz <rschuetz@uni-koblenz.de>
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> === >8 ===
>
> This commit is required to ensure the proper operation of xenstore-related tools.
>
> Would it be possible to include this commit in the patches queued for the next linux-4.4.y release?
Ah, good catch, I'll queue it up after these next releases go out
tomorrow.
thanks,
greg k-h
prev parent reply other threads:[~2016-10-27 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 15:34 A xenbus bug-fix commit missing on the stable/linux-4.4.y branch M. Vefa Bicakci
2016-10-27 16:17 ` Greg KH [this message]
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=20161027161756.GA15284@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=m.v.b@runbox.com \
--cc=stable@vger.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.