On Wed, 2015-12-02 at 17:26 -0600, Matthew R. Ochs wrote:
> From: Dan Carpenter <[email protected]>
> 
> The "> MAX_CONTEXT" should be ">= MAX_CONTEXT".  Otherwise we go one
> step beyond the end of the cfg->ctx_tbl[] array.
> 
> Signed-off-by: Dan Carpenter <[email protected]>
> Reviewed-by: Manoj Kumar <[email protected]>
> Acked-by: Matthew R. Ochs <[email protected]>
> Signed-off-by: Matthew R. Ochs <[email protected]>
> ---
> This patch was originally sent by Dan Carpenter in September 2015. I had
> based my large patch series that went into 4.4 off of it but this patch
> appears to have not made it in. As a valid fix, I'd like to see this make
> it into 'next'. I've gone ahead and performed the rebase so that it
> applies cleanly.
> 
>  drivers/scsi/cxlflash/superpipe.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/scsi/cxlflash/superpipe.c
> b/drivers/scsi/cxlflash/superpipe.c
> index cac2e6a..34b21a0 100644
> --- a/drivers/scsi/cxlflash/superpipe.c
> +++ b/drivers/scsi/cxlflash/superpipe.c
> @@ -1380,7 +1380,7 @@ static int cxlflash_disk_attach(struct scsi_device
> *sdev,
>       }
>  
>       ctxid = cxl_process_element(ctx);
> -     if (unlikely((ctxid > MAX_CONTEXT) || (ctxid < 0))) {
> +     if (unlikely((ctxid >= MAX_CONTEXT) || (ctxid < 0))) {
>               dev_err(dev, "%s: ctxid (%d) invalid!\n", __func__, ctxid);
>               rc = -EPERM;
>               goto err2;
> @@ -1508,7 +1508,7 @@ static int recover_context(struct cxlflash_cfg *cfg,
> struct ctx_info *ctxi)
>       }
>  
>       ctxid = cxl_process_element(ctx);
> -     if (unlikely((ctxid > MAX_CONTEXT) || (ctxid < 0))) {
> +     if (unlikely((ctxid >= MAX_CONTEXT) || (ctxid < 0))) {
>               dev_err(dev, "%s: ctxid (%d) invalid!\n", __func__, ctxid);
>               rc = -EPERM;
>               goto err1;

Reviewed-by: Johannes Thumshirn <[email protected]>
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to