linux-kernel - Re: [PATCH 04/17] Fix use of unallocated memory for MSA2xxx enclosure device data.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20091112144524.dc254708.akpm@linux-foundation.org>
Date:	Thu, 12 Nov 2009 14:45:24 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Stephen M. Cameron" <scameron@...rdog.cce.hp.com>
Cc:	James.Bottomley@...senPartnership.com,
	linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
	mikem@...rdog.cce.hp.com
Subject: Re: [PATCH 04/17] Fix use of unallocated memory for MSA2xxx
 enclosure device data.

On Wed, 11 Nov 2009 10:50:43 -0600
"Stephen M. Cameron" <scameron@...rdog.cce.hp.com> wrote:

> +#define MAX_MSA2XXX_ENCLOSURES 32
> +	if (*nmsa2xxx_enclosures >= MAX_MSA2XXX_ENCLOSURES) {
> +		dev_warn(&h->pdev->dev, "Maximum number of MSA2XXX "
> +			"enclosures exceeded.  Check your hardware "
> +			"configuration.");
> +		return 0;
> +	}

The message would be a bit more helpful if it told the operator what the
limit actually is.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/