From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com,
Ian Campbell <ian.campbell@citrix.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Haogang Chen <haogangchen@gmail.com>
Subject: Re: [Xen-devel] [PATCH 2/2] xen/xenbus: don't reimplement kvasprintf via a fixed size buffer
Date: Wed, 4 Jan 2012 10:12:49 -0500 [thread overview]
Message-ID: <20120104151249.GF3322@phenom.dumpdata.com> (raw)
In-Reply-To: <4F044D10020000780006A5B4@nat28.tlf.novell.com>
On Wed, Jan 04, 2012 at 11:58:56AM +0000, Jan Beulich wrote:
> >>> On 04.01.12 at 12:39, Ian Campbell <ian.campbell@citrix.com> wrote:
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>
> Acked-by: Jan Beulich <jbeulich@suse.com>
OK, took:
Ian Campbell (3):
xen/xenbus: Reject replies with payload > XENSTORE_PAYLOAD_MAX.
xenbus: maximum buffer size is XENSTORE_PAYLOAD_MAX
xen/xenbus: don't reimplement kvasprintf via a fixed size buffer
And put the ' xen/xenbus: Reject replies with payload > XENSTORE_PAYLOAD_MAX'
on the stable@kernel.org as well.
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
Haogang Chen <haogangchen@gmail.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH 2/2] xen/xenbus: don't reimplement kvasprintf via a fixed size buffer
Date: Wed, 4 Jan 2012 10:12:49 -0500 [thread overview]
Message-ID: <20120104151249.GF3322@phenom.dumpdata.com> (raw)
In-Reply-To: <4F044D10020000780006A5B4@nat28.tlf.novell.com>
On Wed, Jan 04, 2012 at 11:58:56AM +0000, Jan Beulich wrote:
> >>> On 04.01.12 at 12:39, Ian Campbell <ian.campbell@citrix.com> wrote:
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
>
> Acked-by: Jan Beulich <jbeulich@suse.com>
OK, took:
Ian Campbell (3):
xen/xenbus: Reject replies with payload > XENSTORE_PAYLOAD_MAX.
xenbus: maximum buffer size is XENSTORE_PAYLOAD_MAX
xen/xenbus: don't reimplement kvasprintf via a fixed size buffer
And put the ' xen/xenbus: Reject replies with payload > XENSTORE_PAYLOAD_MAX'
on the stable@kernel.org as well.
Thanks!
next prev parent reply other threads:[~2012-01-04 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 19:42 [PATCH] XEN: xenbus: integer overflow in process_msg() Haogang Chen
2012-01-04 9:24 ` Ian Campbell
2012-01-04 9:24 ` Ian Campbell
2012-01-04 9:34 ` Ian Campbell
2012-01-04 9:34 ` Ian Campbell
2012-01-04 9:34 ` Ian Campbell
2012-01-04 11:39 ` [PATCH 0/2] xen: Miscelaneous xenbus cleanups Ian Campbell
2012-01-04 11:39 ` Ian Campbell
2012-01-04 11:39 ` [PATCH 1/2] xenbus: maximum buffer size is XENSTORE_PAYLOAD_MAX Ian Campbell
2012-01-04 11:39 ` Ian Campbell
2012-01-04 11:39 ` [PATCH 2/2] xen/xenbus: don't reimplement kvasprintf via a fixed size buffer Ian Campbell
2012-01-04 11:39 ` Ian Campbell
2012-01-04 11:58 ` [Xen-devel] " Jan Beulich
2012-01-04 11:58 ` Jan Beulich
2012-01-04 15:12 ` Konrad Rzeszutek Wilk [this message]
2012-01-04 15:12 ` Konrad Rzeszutek 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=20120104151249.GF3322@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=haogangchen@gmail.com \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/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.