From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Pawel Baldysiak <pawel.baldysiak@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] IMSM: Add warning message when x8-type device is used
Date: Fri, 21 Oct 2016 08:47:37 -0400 [thread overview]
Message-ID: <wrfj4m45q36e.fsf@redhat.com> (raw)
In-Reply-To: <1477042671-12934-1-git-send-email-pawel.baldysiak@intel.com> (Pawel Baldysiak's message of "Fri, 21 Oct 2016 11:37:48 +0200")
Pawel Baldysiak <pawel.baldysiak@intel.com> writes:
> This patch adds the warning message when x8-type device
> is used with IMSM metadata. x8 device is a special
> NVMe drive - two of them on a single PCIe card.
> This card could be a single point of failure for
> RAID levels different than RAID0. x8 devices have
> serial number ending with "-A/-B" or "-1/-2".
>
> Signed-off-by: Pawel Baldysiak <pawel.baldysiak@intel.com>
> Reviewed-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com>
> ---
> super-intel.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 42 insertions(+)
Hi Pawel,
When posting a multi-patch series, it would be helpful to have it sent
with appropriate headers staging the set is X/Y patches and a cover
letter.
I normally use -n --cover-letter
> diff --git a/super-intel.c b/super-intel.c
> index 5c6ab05..e860e75 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -5139,9 +5139,51 @@ static int add_to_super_imsm(struct supertype *st, mdu_disk_info_t *dk,
> rv = imsm_read_serial(fd, devname, dd->serial);
> if (rv) {
> pr_err("failed to retrieve scsi serial, aborting\n");
> + if (dd->devname)
> + free(dd->devname);
> free(dd);
> abort();
> }
> + if (super->hba && ((super->hba->type == SYS_DEV_NVME) ||
> + (super->hba->type == SYS_DEV_VMD))) {
> + int i;
> + char *devpath = diskfd_to_devpath(fd);
> + char controller_path[PATH_MAX];
> +
> + if (!devpath) {
> + pr_err("failed to get devpath, aborting\n");
> + if (dd->devname)
> + free(dd->devname);
> + free(dd);
> + return 1;
> + }
> +
> + snprintf(controller_path, PATH_MAX-1, "%s/device", devpath);
> + free(devpath);
> +
> + if (devpath_to_vendor(controller_path) == 0x8086) {
> + /*
> + * If Intel's NVMe drive has serial ended with
> + * "-A","-B","-1" or "-2" it means that this is "x8"
> + * device (double drive on single PCIe card).
> + * User should be warned about potential data loss.
> + */
> + for (i = MAX_RAID_SERIAL_LEN-1; i > 0; i--) {
> + /* Skip empty character at the end */
> + if (dd->serial[i] == 0)
> + continue;
> +
> + if (((dd->serial[i] == 'A') || (dd->serial[i] == 'B') ||
> + (dd->serial[i] == '1') || (dd->serial[i] == '2')) &&
> + (dd->serial[i-1] == '-'))
Minor nit here - please keep this within 80 characters.
Thanks,
Jes
next prev parent reply other threads:[~2016-10-21 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 9:37 [PATCH] IMSM: Add warning message when x8-type device is used Pawel Baldysiak
2016-10-21 9:37 ` [PATCH] IMSM: Do not update metadata if not able to migrate Pawel Baldysiak
2016-10-21 9:37 ` [PATCH] IMSM: Enable spanning between VMD domains Pawel Baldysiak
2016-10-26 16:03 ` Jes Sorensen
2016-10-21 9:37 ` [PATCH] Lib.c: Fix geting devname for devices with long path Pawel Baldysiak
2016-10-26 16:03 ` Jes Sorensen
2016-10-21 12:47 ` Jes Sorensen [this message]
2016-10-21 14:17 ` [PATCH] IMSM: Add warning message when x8-type device is used Baldysiak, Pawel
2016-10-21 14:22 ` Jes Sorensen
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=wrfj4m45q36e.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=pawel.baldysiak@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).