All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Don Brace <don.brace@microsemi.com>,
	Christoph Hellwig <hch@lst.de>,
	James Bottomley <james.bottomley@hansenpartnership.com>,
	Meelis Roos <mroos@linux.ee>,
	linux-scsi@vger.kernel.org, Jeff Mahoney <jeffm@suse.com>
Subject: Re: [PATCH 6/6] hpsa: handle unsupported devices more gracefully
Date: Wed, 9 Aug 2017 15:48:00 +0200	[thread overview]
Message-ID: <20170809134800.GG25852@lst.de> (raw)
In-Reply-To: <1502181315-102499-7-git-send-email-hare@suse.de>

On Tue, Aug 08, 2017 at 10:35:15AM +0200, Hannes Reinecke wrote:
> From: Jeff Mahoney <jeffm@suse.com>
> 
> Add a warning message if an unsupported device is found and the
> hpsa_allow_any parameter is not set.
> Also make the hpsa_allow_any parameter writeable once the hpsa
> driver is loaded.

This looks ok, but maybe we should also plan for just setting the
flag by defauly sooner or later?

> +static struct kernel_param_ops hpsa_allow_any_ops = {

const?

> +
> +	if (hpsa_allow_any && !newval) {
> +		if (hpsa_claimed_unsupported) {
> +			pr_info("hpsa: can't disable hpsa_allow_any parameter. Devices already in use.\n");
> +			return -EPERM;
> +		} else
> +			hpsa_allow_any = false;
> +	} else if (!hpsa_allow_any && newval) {
> +		pr_info("hpsa: allowing unsupported devices. If devices are claimed, this will result in an unsupported environment.\n");
> +		hpsa_allow_any = true;
> +	}
> +	return 0;

Do we really need this to start with?  It's normal that module
parameters only affect newly probed devices when changed at runtime,
so I think we could just stick to the simple module parameter with
permissions that allow runtime changes.

  reply	other threads:[~2017-08-09 13:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08  8:35 [PATCH RESEND 0/6] hpsa: support legacy boards Hannes Reinecke
2017-08-08  8:35 ` [PATCH 1/6] hpsa: consolidate status variables Hannes Reinecke
2017-08-09 13:40   ` Christoph Hellwig
2017-08-14 10:02     ` Hannes Reinecke
2017-08-08  8:35 ` [PATCH 2/6] hpsa: add support for legacy boards Hannes Reinecke
2017-08-09 13:41   ` Christoph Hellwig
2017-08-09 15:08     ` Hannes Reinecke
2017-08-09 15:59       ` Christoph Hellwig
2017-08-09 13:45   ` Christoph Hellwig
2017-08-09 14:50     ` Hannes Reinecke
2017-08-08  8:35 ` [PATCH 3/6] hpsa: disable volume status check for older controller Hannes Reinecke
2017-08-09 13:42   ` Christoph Hellwig
2017-08-11 13:23   ` Tomas Henzl
2017-08-14 10:45     ` Hannes Reinecke
2017-08-08  8:35 ` [PATCH 4/6] hpsa: Ignore errors for unsupported LV_DEVICE_ID VPD page Hannes Reinecke
2017-08-09 13:45   ` Christoph Hellwig
2017-08-08  8:35 ` [PATCH 5/6] hpsa: do not print errors for unsupported report luns format Hannes Reinecke
2017-08-09 13:46   ` Christoph Hellwig
2017-08-09 14:52     ` Hannes Reinecke
2017-08-08  8:35 ` [PATCH 6/6] hpsa: handle unsupported devices more gracefully Hannes Reinecke
2017-08-09 13:48   ` Christoph Hellwig [this message]
2017-08-09 22:08 ` [PATCH RESEND 0/6] hpsa: support legacy boards Don Brace
2017-08-10  7:07   ` Hannes Reinecke
2017-08-10  7:09     ` Christoph Hellwig
2017-08-10  7:29       ` Hannes Reinecke
2017-08-10 14:06       ` James Bottomley
2017-08-10 14:11         ` Hannes Reinecke
2017-08-10 19:15           ` Don Brace
2017-08-11  6:43             ` Hannes Reinecke
2017-08-11 16:35               ` Don Brace

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=20170809134800.GG25852@lst.de \
    --to=hch@lst.de \
    --cc=don.brace@microsemi.com \
    --cc=hare@suse.de \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=jeffm@suse.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mroos@linux.ee \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.