From: Vishal Verma <vishal.l.verma@intel.com>
To: linux-nvdimm@lists.01.org
Cc: Vishal Verma <vishal.l.verma@intel.com>,
linux-block@vger.kernel.org, linux-raid@vger.kernel.org,
linux-scsi@vger.kernel.org, Jens Axboe <axboe@fb.com>,
NeilBrown <neilb@suse.com>, Jeff Moyer <jmoyer@redhat.com>
Subject: [PATCH 0/3] Badblock tracking for gendisks
Date: Fri, 20 Nov 2015 17:49:17 -0700 [thread overview]
Message-ID: <1448066960-20119-1-git-send-email-vishal.l.verma@intel.com> (raw)
Patch 1 copies badblock management code into a header of its own,
making it generally available. It follows common libraries of code
such as linked lists, where anyone may embed a core data structure
in another place, and use the provided accessor functions to
manipulate the data.
Patch 2 adds badblock tracking to gendisks (in preparation for use
by NVDIMM devices). Right now, it is turned on unconditionally - I'd
appreciate comments on if that is the right path.
Patch 3 converts md over to use the new badblocks 'library'. I have
done some pretty simple testing on this - created a raid 1 device,
made sure the sysfs entries show up, and can be used to add and view
badblocks. A closer look by the md folks would be nice here.
Vishal Verma (3):
badblocks: Add core badblock management code
block: Add badblock management for gendisks
md: convert to use the generic badblocks code
block/genhd.c | 64 ++++++
drivers/md/md.c | 495 ++------------------------------------------
drivers/md/md.h | 31 +--
include/linux/badblocks.h | 512 ++++++++++++++++++++++++++++++++++++++++++++++
include/linux/genhd.h | 6 +
5 files changed, 603 insertions(+), 505 deletions(-)
create mode 100644 include/linux/badblocks.h
--
2.5.0
next reply other threads:[~2015-11-21 0:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 0:49 Vishal Verma [this message]
2015-11-21 0:49 ` [PATCH 1/3] badblocks: Add core badblock management code Vishal Verma
2015-11-24 19:19 ` Jens Axboe
2015-11-21 0:49 ` [PATCH 2/3] block: Add badblock management for gendisks Vishal Verma
2015-11-24 15:34 ` Jeff Moyer
2015-11-24 19:03 ` Verma, Vishal L
2015-11-24 19:14 ` Jeff Moyer
2015-11-24 20:10 ` Verma, Vishal L
2015-11-24 21:31 ` Dan Williams
2015-11-25 15:37 ` Jeff Moyer
2015-11-25 17:55 ` Verma, Vishal L
2015-11-25 18:07 ` Jeff Moyer
2015-11-21 0:49 ` [PATCH 3/3] md: convert to use the generic badblocks code Vishal Verma
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=1448066960-20119-1-git-send-email-vishal.l.verma@intel.com \
--to=vishal.l.verma@intel.com \
--cc=axboe@fb.com \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=neilb@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).