From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Roger Pau Monne <roger.pau@citrix.com>,
mrushton@amazon.com, msw@amazon.com
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH v2 0/4] xen-blk: bug fixes
Date: Tue, 4 Feb 2014 11:15:01 -0400 [thread overview]
Message-ID: <20140204151501.GA1781@andromeda.dapyr.net> (raw)
In-Reply-To: <1391509575-3949-1-git-send-email-roger.pau@citrix.com>
On Tue, Feb 04, 2014 at 11:26:11AM +0100, Roger Pau Monne wrote:
> This series contain blkback bug fixes for memory leaks (patches 1 and
> 2) and a race (patch 3). Patch 4 removes blkif_request_segment_aligned
> since its memory layout is exactly the same as blkif_request_segment
> and should introduce no functional change.
>
> All patches should be backported to stable branches, although the last
> one is not a functional change it will still be nice to have it for
> code correctness.
Matt and Matt, could you guys kindly take a look as well? Thank you!
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-02-04 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 10:26 Roger Pau Monne
2014-02-04 10:26 ` [PATCH v2 1/4] xen-blkback: fix memory leak when persistent grants are used Roger Pau Monne
2014-02-04 10:30 ` David Vrabel
2014-02-04 10:26 ` [PATCH v2 2/4] xen-blkback: fix memory leaks Roger Pau Monne
2014-02-04 10:32 ` David Vrabel
2014-02-04 10:26 ` [PATCH v2 3/4] xen-blkback: fix shutdown race Roger Pau Monne
2014-02-04 10:34 ` David Vrabel
2014-02-04 10:26 ` [PATCH v2 4/4] xen-blkif: drop struct blkif_request_segment_aligned Roger Pau Monne
2014-02-04 10:35 ` David Vrabel
2014-02-04 15:15 ` Konrad Rzeszutek Wilk [this message]
2014-02-06 4:57 ` [Xen-devel] [PATCH v2 0/4] xen-blk: bug fixes Matt Wilson
2014-02-06 16:20 ` Konrad Rzeszutek Wilk
2014-02-07 4:24 ` Matt Wilson
2014-02-07 8:08 ` Roger Pau Monné
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=20140204151501.GA1781@andromeda.dapyr.net \
--to=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrushton@amazon.com \
--cc=msw@amazon.com \
--cc=roger.pau@citrix.com \
--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
Powered by JetHome