From: NeilBrown <neilb@suse.de>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
ed.ciechanowski@intel.com, wojciech.neubauer@intel.com
Subject: Re: [PATCH 1/7] FIX: Verify Backup file name before reshape
Date: Wed, 2 Mar 2011 12:01:33 +1100 [thread overview]
Message-ID: <20110302120133.74ef2c89@notabene.brown> (raw)
In-Reply-To: <20110301145650.10678.1741.stgit@gklab-128-013.igk.intel.com>
On Tue, 01 Mar 2011 15:56:50 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
> When reshape is continued backup_file is required for user data safety.
> Grow_continue() has to verify if any file name is passed in.
>
> Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> ---
>
> Grow.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/Grow.c b/Grow.c
> index 47b8809..1470a91 100644
> --- a/Grow.c
> +++ b/Grow.c
> @@ -3332,6 +3332,11 @@ int Grow_continue(int mdfd, struct supertype *st, struct mdinfo *info,
> char *container = NULL;
> int err;
>
> + if (backup_file == NULL) {
> + fprintf(stderr, Name ": Backup file name has to be specified "
> + "for reshape continuation.\n");
> + return 1;
> + }
> if (!st->ss->external) {
> err = sysfs_set_str(info, NULL, "array_state", "readonly");
> if (err)
reshape_array already performs checks to ensure that backup_file is set when
needed - it isn't always needed.
Is there some reason those checks are not enough?
NeilBrown
next prev parent reply other threads:[~2011-03-02 1:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 14:56 [PATCH 0/7] Grow_continue, use in assembly (cont.) Adam Kwolek
2011-03-01 14:56 ` [PATCH 1/7] FIX: Verify Backup file name before reshape Adam Kwolek
2011-03-02 1:01 ` NeilBrown [this message]
2011-03-02 7:39 ` Kwolek, Adam
2011-03-01 14:56 ` [PATCH 2/7] FIX: reshape in md should wait for monitoring process (external metadata) Adam Kwolek
2011-03-02 1:06 ` NeilBrown
2011-03-01 14:57 ` [PATCH 3/7] FIX: configure disks slot for expansion Adam Kwolek
2011-03-02 1:10 ` NeilBrown
2011-03-02 7:48 ` Kwolek, Adam
2011-03-01 14:57 ` [PATCH 4/7] Add block_subarray() Adam Kwolek
2011-03-01 14:57 ` [PATCH 5/7] FIX: Block monitor when starting array with reshape in progress Adam Kwolek
2011-03-01 14:57 ` [PATCH 6/7] Continue reshape after assembling array Adam Kwolek
2011-03-01 14:57 ` [PATCH 7/7] FIX: array is frozen after reshape Adam Kwolek
2011-03-02 1:30 ` [PATCH 0/7] Grow_continue, use in assembly (cont.) NeilBrown
2011-03-02 7:49 ` Kwolek, Adam
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=20110302120133.74ef2c89@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=wojciech.neubauer@intel.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).