From: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
To: shli@kernel.org
Cc: linux-raid@vger.kernel.org,
Artur Paszkiewicz <artur.paszkiewicz@intel.com>
Subject: [PATCH 08/12] md: expose rdev->sb_start as sysfs attribute
Date: Thu, 24 Nov 2016 13:28:43 +0100 [thread overview]
Message-ID: <20161124122847.16456-9-artur.paszkiewicz@intel.com> (raw)
In-Reply-To: <20161124122847.16456-1-artur.paszkiewicz@intel.com>
This is meant for external metadata arrays, to pass the location of the
superblock to the kernel.
Signed-off-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
---
drivers/md/md.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 5a14f8e..7049833 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -3204,6 +3204,27 @@ static ssize_t ubb_store(struct md_rdev *rdev, const char *page, size_t len)
static struct rdev_sysfs_entry rdev_unack_bad_blocks =
__ATTR(unacknowledged_bad_blocks, S_IRUGO|S_IWUSR, ubb_show, ubb_store);
+static ssize_t
+sb_start_show(struct md_rdev *rdev, char *page)
+{
+ return sprintf(page, "%llu\n", (unsigned long long)rdev->sb_start);
+}
+
+static ssize_t
+sb_start_store(struct md_rdev *rdev, const char *buf, size_t len)
+{
+ unsigned long long sb_start;
+ if (kstrtoull(buf, 10, &sb_start) < 0)
+ return -EINVAL;
+ if (!rdev->mddev->external)
+ return -EBUSY;
+ rdev->sb_start = sb_start;
+ return len;
+}
+
+static struct rdev_sysfs_entry rdev_sb_start =
+__ATTR(sb_start, S_IRUGO|S_IWUSR, sb_start_show, sb_start_store);
+
static struct attribute *rdev_default_attrs[] = {
&rdev_state.attr,
&rdev_errors.attr,
@@ -3214,6 +3235,7 @@ static struct attribute *rdev_default_attrs[] = {
&rdev_recovery_start.attr,
&rdev_bad_blocks.attr,
&rdev_unack_bad_blocks.attr,
+ &rdev_sb_start.attr,
NULL,
};
static ssize_t
--
2.10.1
next prev parent reply other threads:[~2016-11-24 12:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 12:28 [PATCH 00/12] Partial Parity Log for MD RAID 5 Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 01/12] raid5-cache: move declarations to separate header Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 02/12] raid5-cache: add policy logic Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 03/12] raid5-cache: add a new policy Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 04/12] md: superblock changes for PPL Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 05/12] raid5-ppl: Partial Parity Log implementation Artur Paszkiewicz
2016-11-25 2:26 ` kbuild test robot
2016-11-25 8:52 ` Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 06/12] raid5-ppl: calculate partial parity Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 07/12] md: mddev_find_container helper function Artur Paszkiewicz
2016-11-24 12:28 ` Artur Paszkiewicz [this message]
2016-11-24 12:28 ` [PATCH 09/12] raid5-ppl: read PPL signature from IMSM metadata Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 10/12] raid5-ppl: recovery from dirty shutdown using PPL Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 11/12] raid5-ppl: support disk add/remove with distributed PPL Artur Paszkiewicz
2016-11-24 12:28 ` [PATCH 12/12] raid5-ppl: runtime PPL enabling or disabling Artur Paszkiewicz
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=20161124122847.16456-9-artur.paszkiewicz@intel.com \
--to=artur.paszkiewicz@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=shli@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;
as well as URLs for NNTP newsgroup(s).