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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <yq1y4pbznbq.fsf@sermon.lab.mkp.net>
Date:	Fri, 09 Jan 2015 15:55:05 -0500
From:	"Martin K. Petersen" <martin.petersen@...cle.com>
To:	Sreekanth Reddy <sreekanth.reddy@...gotech.com>
Cc:	martin.petersen@...cle.com, jejb@...nel.org, hch@...radead.org,
	linux-scsi@...r.kernel.org, JBottomley@...allels.com,
	Sathya.Prakash@...gotech.com, Nagalakshmi.Nandigama@...gotech.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 06/22] [SCSI] mpt2sas, mpt3sas: Removing uppper boundary restriction for the module parameter max_sgl_entries

>>>>> "Sreekanth" == Sreekanth Reddy <sreekanth.reddy@...gotech.com> writes:

Sreekanth> 1. Extended the upper boundary restriction for the module
Sreekanth> parameter max_sgl_entries.  Earlier, the max_sgl_entries was
Sreekanth> capped at the SCSI_MAX_SG_SEGMENTS kernel definition.  With
Sreekanth> this change, the user would be able to set the
Sreekanth> max_sgl_entries to any value which is greater than
Sreekanth> SCSI_MAX_SG_SEGMENTS and less than the minimum of
Sreekanth> SCSI_MAX_SG_CHAIN_SEGMENTS & hardware limit(Calculated using
Sreekanth> IOCFacts's MaxChainDepth).

Sreekanth> 2. Added a print for the message log whenever the user sets
Sreekanth> the max_sgl_entries to a value greater than
Sreekanth> SCSI_MAX_SG_SEGMENTS to warn about the kernel definition
Sreekanth> overriding.

Reviewed-by: Martin K. Petersen <martin.petersen@...cle.com>

-- 
Martin K. Petersen	Oracle Linux Engineering
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ