From: Daniel Stodden <daniel.stodden@citrix.com>
To: Xen <xen-devel@lists.xensource.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: [PATCH 0 of 8] Linux/pvops blktap + blkfront updates.
Date: Fri, 26 Feb 2010 16:04:48 -0000 [thread overview]
Message-ID: <patchbomb.1267200288@agari.van.xensource.com> (raw)
First 4 stop blktap barfing once and blkfront twice during shutdown,
plus a memory leak.
16 A fix-double-free.diff: blktap: Fix tap kobj double unref in sysfs_destroy.
17 A fix-blk-cleanup.diff: blkfront: Fix backtrace in blk_cleanup_queue.
18 A fix-gendisk-leak.diff: blkfront: Stop leaking the gendisk struct.
19 A fix-bd-oops.diff: blkfront: Fix an unlikely xenbus crasher.
The rest is decoration.
20 A blkfront-close.diff: blkfront: Clean up closing transition.
21 A xs-write-unlocked.diff: blkfront: Move xenstore accesses off the device release path.
22 A xlvbd-release-gendisk.diff: blkfront: Clean up blkfront_closing.
23 A debug-common.diff: blkfront: Clean up debug statements.
Cheers,
Daniel
next reply other threads:[~2010-02-26 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 16:04 Daniel Stodden [this message]
2010-02-26 16:04 ` [PATCH 1 of 8] blktap: Fix tap kobj double unref in sysfs_destroy Daniel Stodden
2010-02-26 16:04 ` [PATCH 2 of 8] blkfront: Fix backtrace in blk_cleanup_queue Daniel Stodden
2010-02-26 16:04 ` [PATCH 3 of 8] blkfront: Stop leaking the gendisk struct Daniel Stodden
2010-02-26 16:04 ` [PATCH 4 of 8] blkfront: Fix an unlikely xenbus crasher Daniel Stodden
2010-02-26 16:04 ` [PATCH 5 of 8] blkfront: Clean up closing transition Daniel Stodden
2010-02-26 16:04 ` [PATCH 6 of 8] blkfront: Move xenstore accesses off the device release path Daniel Stodden
2010-02-26 16:04 ` [PATCH 7 of 8] blkfront: Clean up blkfront_closing Daniel Stodden
2010-02-26 16:04 ` [PATCH 8 of 8] blkfront: Clean up debug statements Daniel Stodden
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=patchbomb.1267200288@agari.van.xensource.com \
--to=daniel.stodden@citrix.com \
--cc=jeremy@goop.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.