From: Andre Noll <maan@systemlinux.org>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [md PATCH 14/22] md: support updating bitmap parameters via sysfs.
Date: Tue, 8 Dec 2009 11:29:43 +0100 [thread overview]
Message-ID: <20091208102943.GZ21495@skl-net.de> (raw)
In-Reply-To: <20091204064802.10264.47719.stgit@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 4969 bytes --]
On 17:48, NeilBrown wrote:
> A new attribute directory 'bitmap' in 'md' is created which
> contains files for configuring the bitmap.
Nice.
> 'location' identifies where the bitmap is, either 'none',
> or 'file' or 'sector offset from metadata'.
> Writing 'location' can create or remove a bitmap.
> Adding a 'file' bitmap this way is not yet supported.
>
> 'chunksize' can be set before creating a bitmap, but is
> currently always over-ridden by the bitmap superblock.
>
> 'time_base' and 'backlog' can be updated at any time.
This text should probably go into the mdadm documentation as well.
> +static ssize_t
> +location_show(mddev_t *mddev, char *page)
> +{
> + ssize_t len = 0;
> + if (mddev->bitmap_info.file) {
> + len = sprintf(page, "file");
> + } else if (mddev->bitmap_info.offset) {
> + len = sprintf(page, "%+lld", (long long)mddev->bitmap_info.offset);
> + } else
> + len = sprintf(page, "none");
> + len += sprintf(page+len, "\n");
> + return len;
> +}
Pointless initialization to zero.
> + } else {
> + /* No bitmap, OK to set a location */
> + long long offset;
> + if (strncmp(buf, "none", 4) == 0)
> + /* nothing to be done */;
> + else if (strncmp(buf, "file:", 5) == 0) {
> + /* Not supported yet */
> + return -EINVAL;
> + } else {
> + int rv;
> + if (buf[0] == '+')
> + rv = strict_strtoll(buf+1, 10, &offset);
> + else
> + rv = strict_strtoll(buf, 10, &offset);
> + if (rv)
> + return rv;
> + mddev->bitmap_info.offset = offset;
Introducing a sanity check here would probably save some sysadmin's
feet.
> +static struct md_sysfs_entry bitmap_location =
> +__ATTR(location, S_IRUGO|S_IWUSR, location_show, location_store);
> +
> +static ssize_t
> +timeout_show(mddev_t *mddev, char *page)
> +{
> + ssize_t len = 0;
> + unsigned long secs = mddev->bitmap_info.daemon_sleep / HZ;
> + unsigned long jifs = mddev->bitmap_info.daemon_sleep % HZ;
> +
> + len = sprintf(page, "%lu", secs);
> + if (jifs)
> + len += sprintf(page+len, ".%03u", jiffies_to_msecs(jifs));
> + len += sprintf(page+len, "\n");
> + return len;
> +}
Again, no need to initialize len.
> +
> +int strict_strtoul_scaled(const char *cp, unsigned long *res, int scale)
> +{
> + unsigned long result = 0;
> + long decimals = -1;
> + while (isdigit(*cp) || (*cp == '.' && decimals < 0)) {
> + if (*cp == '.')
> + decimals = 0;
> + else if (decimals < scale) {
> + unsigned int value;
> + value = *cp - '0';
> + result = result * 10 + value;
> + if (decimals >= 0)
> + decimals++;
> + }
> + cp++;
> + }
> + if (*cp == '\n')
> + cp++;
> + if (*cp)
> + return -EINVAL;
> + if (decimals < 0)
> + decimals = 0;
> + while (decimals < scale) {
> + result *= 10;
> + decimals ++;
> + }
> + *res = result;
> + return 0;
> +}
A comment which describes what exactly this function is supposed to
to would be nice. It has only one caller and could be made static BTW.
OTOH, it probably belongs to lib/vsprintf.c.
> +static ssize_t
> +timeout_store(mddev_t *mddev, const char *buf, size_t len)
> +{
> + /* timeout can be set at any time */
> + unsigned long timeout;
> + int rv = strict_strtoul_scaled(buf, &timeout, 4);
> + if (rv)
> + return rv;
> +
> + timeout = timeout * HZ / 10000;
This might overflow. But maybe that's OK as only insane values (written
by root) will cause an overflow.
> +
> + if (timeout > MAX_SCHEDULE_TIMEOUT)
> + timeout = MAX_SCHEDULE_TIMEOUT;
> + if (timeout < 1)
> + timeout = 1;
> + mddev->bitmap_info.daemon_sleep = timeout;
> + if (mddev->thread) {
> + if (mddev->thread->timeout < MAX_SCHEDULE_TIMEOUT) {
> + mddev->thread->timeout = timeout;
> + md_wakeup_thread(mddev->thread);
> + }
I don't get this. Why do we want to set mddev->thread->timeout only
if mddev->thread->timeout < MAX_SCHEDULE_TIMEOUT)?
Also, if the timeout is being set while the array is stopped, the
command succeeds but has no effect (as mddev->thread is NULL). Maybe
it's better to return an error in this case.
> +static ssize_t
> +backlog_store(mddev_t *mddev, const char *buf, size_t len)
> +{
> + unsigned long backlog;
> + int rv = strict_strtoul(buf, 10, &backlog);
> + if (rv)
> + return rv;
> + if (backlog > COUNTER_MAX)
> + backlog = COUNTER_MAX;
> + mddev->bitmap_info.max_write_behind = backlog;
> + return len;
> +}
If the given value is too large this code silently ignores that value
and uses the maximal possible value instead. Even if we'd prefer "I
know better what you really want" over "you asked for it you got it",
we should at least be consistent. min_sync_store() for example returns
EINVAL if the given value is not suitable. So does chunksize_store()
below.
The same comment applies to timeout_store() of course.
Regards
Andre
--
The only person who always got his work done by Friday was Robinson Crusoe
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-12-08 10:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 6:48 [md PATCH 00/22] MD patches queued for 2.6.33 NeilBrown
2009-12-04 6:48 ` [md PATCH 05/22] md/raid5: don't complete make_request on barrier until writes are scheduled NeilBrown
2010-01-21 21:07 ` [md PATCH 05/22] md/raid5: don't complete make_request on barrieruntil " Tirumala Reddy Marri
2010-01-28 2:44 ` Neil Brown
2009-12-04 6:48 ` [md PATCH 03/22] md: don't reset curr_resync_completed after an interrupted resync NeilBrown
2009-12-04 6:48 ` [md PATCH 02/22] md: adjust resync_min usefully when resync aborts NeilBrown
2009-12-04 6:48 ` [md PATCH 09/22] md: collect bitmap-specific fields into one structure NeilBrown
2009-12-04 6:48 ` [md PATCH 04/22] md: support barrier requests on all personalities NeilBrown
2009-12-08 13:54 ` Andre Noll
2009-12-10 6:25 ` Neil Brown
2009-12-11 11:46 ` Andre Noll
2009-12-04 6:48 ` [md PATCH 11/22] md: change daemon_sleep to be in 'jiffies' rather than 'seconds' NeilBrown
2009-12-04 6:48 ` [md PATCH 01/22] md/bitmap: protect against bitmap removal while being updated NeilBrown
2009-12-04 6:48 ` [md PATCH 16/22] md/bitmap: update dirty flag when bitmap bits are explicitly set NeilBrown
2009-12-04 6:48 ` [md PATCH 22/22] md: integrate spares into array at earliest opportunity NeilBrown
2009-12-04 6:48 ` [md PATCH 13/22] md: support bitmap offset appropriate for external-metadata arrays NeilBrown
2009-12-04 6:48 ` [md PATCH 21/22] md: move compat_ioctl handling into md.c NeilBrown
2009-12-04 6:48 ` [md PATCH 19/22] md: add MODULE_DESCRIPTION for all md related modules NeilBrown
2009-12-04 6:48 ` [md PATCH 07/22] md/raid1: add takeover support for raid5->raid1 NeilBrown
2009-12-04 6:48 ` [md PATCH 10/22] md: move offset, daemon_sleep and chunksize out of bitmap structure NeilBrown
2009-12-04 6:48 ` [md PATCH 18/22] raid: improve MD/raid10 handling of correctable read errors NeilBrown
2009-12-04 6:48 ` [md PATCH 20/22] md: revise Kconfig help for MD_MULTIPATH NeilBrown
2009-12-04 6:48 ` [md PATCH 06/22] md: add honouring of suspend_{lo,hi} to raid1 NeilBrown
2009-12-04 6:48 ` [md PATCH 12/22] md: remove needless setting of thread->timeout in raid10_quiesce NeilBrown
2009-12-04 6:48 ` [md PATCH 14/22] md: support updating bitmap parameters via sysfs NeilBrown
2009-12-08 10:29 ` Andre Noll [this message]
2009-12-10 6:14 ` Neil Brown
2009-12-11 11:46 ` Andre Noll
2009-12-04 6:48 ` [md PATCH 17/22] md/raid10: print more useful messages on device failure NeilBrown
2009-12-04 6:48 ` [md PATCH 15/22] md: Support write-intent bitmaps with externally managed metadata NeilBrown
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=20091208102943.GZ21495@skl-net.de \
--to=maan@systemlinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).