From: Frederic Weisbecker <frederic@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Josh Triplett <josh@joshtriplett.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] locktorture: Check the correct variable for allocation failure
Date: Thu, 28 Sep 2023 15:00:47 +0200 [thread overview]
Message-ID: <ZRV4/20T4pGk2QuX@lothringen> (raw)
In-Reply-To: <ec2c9ecf-9360-41fa-934d-6854d2615799@moroto.mountain>
On Thu, Sep 28, 2023 at 10:06:11AM +0300, Dan Carpenter wrote:
> There is a typo so this checks the wrong variable. "chains" plural vs
> "chain" singular. We already know that "chains" is non-zero.
>
> Fixes: 7f993623e9eb ("locktorture: Add call_rcu_chains module parameter")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> kernel/locking/locktorture.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c
> index a3abcd136f56..69d3cd2cfc3b 100644
> --- a/kernel/locking/locktorture.c
> +++ b/kernel/locking/locktorture.c
> @@ -1075,7 +1075,7 @@ static int call_rcu_chain_init(void)
> if (call_rcu_chains <= 0)
> return 0;
> call_rcu_chain = kcalloc(call_rcu_chains, sizeof(*call_rcu_chain), GFP_KERNEL);
> - if (!call_rcu_chains)
> + if (!call_rcu_chain)
> return -ENOMEM;
> for (i = 0; i < call_rcu_chains; i++) {
> call_rcu_chain[i].crc_stop = false;
Oh good catch, queueing this one, thanks!
prev parent reply other threads:[~2023-09-28 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 7:06 [PATCH] locktorture: Check the correct variable for allocation failure Dan Carpenter
2023-09-28 13:00 ` Frederic Weisbecker [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=ZRV4/20T4pGk2QuX@lothringen \
--to=frederic@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=dave@stgolabs.net \
--cc=josh@joshtriplett.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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