From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-scsi@vger.kernel.org, Dick Kennedy <dick.kennedy@broadcom.com>
Subject: Re: [PATCH] lpfc: size cpu map by last cpu id set
Date: Thu, 21 Nov 2019 20:51:10 -0500 [thread overview]
Message-ID: <yq17e3sd6gh.fsf@oracle.com> (raw)
In-Reply-To: <20191121175556.18953-1-jsmart2021@gmail.com> (James Smart's message of "Thu, 21 Nov 2019 09:55:56 -0800")
James,
> Currently the lpfc driver sizes its cpu_map array based on
> num_possible_cpus(). However, that can be a value that is less than
> the highest cpu id bit that is set. As such, if a thread runs on a cpu
> with a larger cpu id, or for_each_possible_cpu() is used, the driver
> could index off the end of the array and return garbage or GPF.
Applied to 5.5/scsi-queue, thanks.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-11-22 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 17:55 [PATCH] lpfc: size cpu map by last cpu id set James Smart
2019-11-21 22:11 ` Ewan D. Milne
2019-11-22 1:51 ` Martin K. Petersen [this message]
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=yq17e3sd6gh.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=dick.kennedy@broadcom.com \
--cc=jsmart2021@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).