mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	fenghua.yu@intel.com
Cc: rex.zhang@intel.com, dave.jiang@intel.com, tony.luck@intel.com,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	dmaengine@vger.kernel.org
Subject: Re: [PATCH] crypto: iaa - Account for cpu-less numa nodes
Date: Tue, 26 Dec 2023 13:09:46 -0800	[thread overview]
Message-ID: <ba080e23-18b1-4ab5-baa8-62bc09a98e38@infradead.org> (raw)
In-Reply-To: <00e3eea06f5dde61734a53af797b190692060aab.camel@linux.intel.com>

Hi--

On 12/26/23 12:53, Tom Zanussi wrote:
> In some configurations e.g. systems with CXL, a numa node can have 0
> cpus and cpumask_nth() will return a cpu value that doesn't exist,
> which will result in an attempt to add an entry to the wq table at a
> bad index.
> 
> To fix this, when iterating the cpus for a node, skip any node that
> doesn't have cpus.
> 
> Also, as a precaution, add a warning and bail if cpumask_nth() returns
> a nonexistent cpu.
> 
> Reported-by: Zhang, Rex <rex.zhang@intel.com>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> ---
>  drivers/crypto/intel/iaa/iaa_crypto_main.c | 14 +++++++++++---
>  1 file changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/crypto/intel/iaa/iaa_crypto_main.c b/drivers/crypto/intel/iaa/iaa_crypto_main.c
> index 5093361b0107..782157a74043 100644
> --- a/drivers/crypto/intel/iaa/iaa_crypto_main.c
> +++ b/drivers/crypto/intel/iaa/iaa_crypto_main.c
> @@ -1017,12 +1017,17 @@ static void rebalance_wq_table(void)
>  		return;
>  	}
>  
> -	for_each_online_node(node) {
> +	for_each_node_with_cpus(node) {
>  		node_cpus = cpumask_of_node(node);
>  
>  		for (cpu = 0; cpu < nr_cpus_per_node; cpu++) {
>  			int node_cpu = cpumask_nth(cpu, node_cpus);
>  
> +			if (WARN_ON(node_cpu >= nr_cpu_ids)) {
> +				pr_debug("node_cpu %d doesn't exist!\n", node_cpu);
> +				return;
> +			}
> +
>  			if ((cpu % cpus_per_iaa) == 0)
>  				iaa++;
>  
> @@ -2095,10 +2100,13 @@ static struct idxd_device_driver iaa_crypto_driver = {
>  static int __init iaa_crypto_init_module(void)
>  {
>  	int ret = 0;
> +	int node;
>  
>  	nr_cpus = num_online_cpus();
> -	nr_nodes = num_online_nodes();
> -	nr_cpus_per_node = nr_cpus / nr_nodes;
> +	for_each_node_with_cpus(node)
> +		nr_nodes++;
> +	if (nr_nodes)
> +		nr_cpus_per_node = nr_cpus / nr_nodes;

If nr_nodes == 0, nr_cpus_per_node is not initialized here.
Is it initialized somewhere else, or just not used if nr_nodes is 0?

>  
>  	if (crypto_has_comp("deflate-generic", 0, 0))
>  		deflate_generic_tfm = crypto_alloc_comp("deflate-generic", 0, 0);

-- 
#Randy

  reply	other threads:[~2023-12-26 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-26 20:53 Tom Zanussi
2023-12-26 21:09 ` Randy Dunlap [this message]
2023-12-26 22:04   ` Tom Zanussi
2023-12-26 23:24     ` Randy Dunlap
2023-12-29  3:31 ` Herbert Xu

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=ba080e23-18b1-4ab5-baa8-62bc09a98e38@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rex.zhang@intel.com \
    --cc=tom.zanussi@linux.intel.com \
    --cc=tony.luck@intel.com \
    /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

all inboxes | Powered by JetHome®