linux-kernel - Re: [PATCH] cciss: Initialize scsi host max

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: <20120321144431.044d3af3.akpm@linux-foundation.org>
Date:	Wed, 21 Mar 2012 14:44:31 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"Stephen M. Cameron" <scameron@...rdog.cce.hp.com>
Cc:	axboe@...nel.dk, stephenmcameron@...il.com,
	mikem@...rdog.cce.hp.com, linux-kernel@...r.kernel.org,
	thenzl@...hat.com
Subject: Re: [PATCH] cciss: Initialize scsi host max_sectors for tape drive
 support

On Wed, 21 Mar 2012 16:32:03 -0500
"Stephen M. Cameron" <scameron@...rdog.cce.hp.com> wrote:

> From: Stephen M. Cameron <scameron@...rdog.cce.hp.com>
> 
> The default is too small

So is the changelog.

> (1024 blocks), use h->cciss_max_sectors (8192 blocks)

What problem does this patch solve?  What might be the user-visible
effects of the change?

> Signed-off-by: Stephen M. Cameron <scameron@...rdog.cce.hp.com>
> ---
>  drivers/block/cciss_scsi.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/block/cciss_scsi.c b/drivers/block/cciss_scsi.c
> index e820b68..f510a9c 100644
> --- a/drivers/block/cciss_scsi.c
> +++ b/drivers/block/cciss_scsi.c
> @@ -866,6 +866,7 @@ cciss_scsi_detect(ctlr_info_t *h)
>  	sh->can_queue = cciss_tape_cmds;
>  	sh->sg_tablesize = h->maxsgentries;
>  	sh->max_cmd_len = MAX_COMMAND_SIZE;
> +	sh->max_sectors = h->cciss_max_sectors;
>  
>  	((struct cciss_scsi_adapter_data_t *) 
>  		h->scsi_ctlr)->scsi_host = sh;
--
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/