From: Ed Cashin <ecashin@coraid.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, ecashin@coraid.com
Subject: [PATCH 0/6] aoe: add debugfs-based export of debug counters
Date: Tue, 23 Jul 2013 17:06:53 -0400 [thread overview]
Message-ID: <cover.1374610591.git.ecashin@coraid.com> (raw)
This patch series applies to today's linux-next/akpm, commit
0c2f52fa9a7cb139617078568c48026c49927617.
It adds the debugging information that the coraid.com-distributed aoe
driver exports via sysfs, but instead of sysfs, it uses debugfs.
With these patches applied, even without AoE targets on the network,
KEDR reports new possible memory leaks, but these are from callers
outside the aoe driver that have used aoe_devnode to get the name of
the character devices through the aoe_class->devnode callback, and I
believe they're responsible for freeing that memory.
Ed L. Cashin (6):
aoe: create and destroy debugfs directory for aoe
aoe: add AoE-target files to debugfs
aoe: provide file operations for debugfs files
aoe: fill in per-AoE-target information for debugfs file
aoe: update copyright date
aoe: update internal version number to 85
drivers/block/aoe/aoe.h | 4 +-
drivers/block/aoe/aoeblk.c | 101 +++++++++++++++++++++++++++++++++++++++++++-
drivers/block/aoe/aoedev.c | 1 +
3 files changed, 103 insertions(+), 3 deletions(-)
next reply other threads:[~2013-07-23 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 21:06 Ed Cashin [this message]
2013-07-23 21:09 ` [PATCH 1/6] aoe: create and destroy debugfs directory for aoe Ed Cashin
2013-07-23 21:11 ` [PATCH 2/6] aoe: add AoE-target files to debugfs Ed Cashin
2013-07-23 21:13 ` [PATCH 3/6] aoe: provide file operations for debugfs files Ed Cashin
2013-07-23 21:15 ` [PATCH 4/6] aoe: fill in per-AoE-target information for debugfs file Ed Cashin
2013-07-23 21:17 ` [PATCH 5/6] aoe: update copyright date Ed Cashin
2013-07-23 21:19 ` [PATCH 6/6] aoe: update internal version number to 85 Ed Cashin
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=cover.1374610591.git.ecashin@coraid.com \
--to=ecashin@coraid.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox