public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Don't register integrity profile for disabled disks
Date: Wed, 06 Aug 2008 11:17:49 -0700	[thread overview]
Message-ID: <1218046669.7493.36.camel@localhost.localdomain> (raw)
In-Reply-To: <yq1y73auid5.fsf@sermon.lab.mkp.net>

On Wed, 2008-08-06 at 14:08 -0400, Martin K. Petersen wrote:
> Avoid registering a block integrity profile if the disk has been
> disabled earlier in the probe process.

This is a possible thing to have happen for devices with SCSI-2
reservations ... and that's not a permanenet condition.  When the
reservation is released, tools usually do a BLKRRPART, but that won't
pick up the DIF information ... perhaps this should be in
sd_revalidate_disk?

James



  reply	other threads:[~2008-08-06 18:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 18:08 [PATCH] Don't register integrity profile for disabled disks Martin K. Petersen
2008-08-06 18:17 ` James Bottomley [this message]
2008-08-06 18:46   ` Martin K. Petersen

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=1218046669.7493.36.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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