public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Gregory Price <gourry.memverge@gmail.com>
Cc: linux-kernel@vger.kernel.org, rafael@kernel.org,
	Gregory Price <gregory.price@memverge.com>
Subject: Re: [PATCH] base/node.c: initialize the accessor list before registering
Date: Tue, 31 Oct 2023 07:03:17 +0100	[thread overview]
Message-ID: <2023103129-coming-geometric-8ac0@gregkh> (raw)
In-Reply-To: <20231030044239.971756-1-gregory.price@memverge.com>

On Mon, Oct 30, 2023 at 12:42:39AM -0400, Gregory Price wrote:
> The current code registers the node as available in the node array
> before initializing the accessor list.  This makes it so that
> anything which might access the accessor list as a result of
> allocations will cause an undefined memory access.
> 
> In one example, an extension to access hmat data during interleave
> caused this undefined access as a result of a bulk allocation
> that occurs during node initialization but before the accessor
> list is initialized.

Is this an in-kernel driver that causes this problem?

> 
> Initialize the accessor list before making the node generally
> available to the global system.
> 
> Signed-off-by: Gregory Price <gregory.price@memverge.com>

What commit id does this fix?

thanks,

greg k-h

  reply	other threads:[~2023-10-31  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  4:42 [PATCH] base/node.c: initialize the accessor list before registering Gregory Price
2023-10-31  6:03 ` Greg KH [this message]
2023-10-31  4:58   ` Gregory Price

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=2023103129-coming-geometric-8ac0@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=gourry.memverge@gmail.com \
    --cc=gregory.price@memverge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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