mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Yichun Zhang (agentzh)" <yichun@openresty.com>,
	linux-fsdevel@vger.kernel.org
Cc: Colin Ian King <colin.i.king@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] relay: replay_file_open(): NULL ptr deref in CPU hotplugs
Date: Thu, 8 Sep 2022 15:19:55 -0600	[thread overview]
Message-ID: <995450c5-a4f2-d2d1-8a44-569726eb7231@kernel.dk> (raw)
In-Reply-To: <20220908211731.11534-1-yichun@openresty.com>

On 9/8/22 3:17 PM, Yichun Zhang (agentzh) wrote:
> CPU hotplug may introduce race conditions. We reproduced kernel panics
> due to this NULL ptr deref error when doing frequent random CPU hotplugs
> in a KVM guest.
> 
> Signed-off-by: Yichun Zhang (agentzh) <yichun@openresty.com>
> ---
>  kernel/relay.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/kernel/relay.c b/kernel/relay.c
> index 6a611e779e95..2db69fd527d1 100644
> --- a/kernel/relay.c
> +++ b/kernel/relay.c
> @@ -816,6 +816,9 @@ EXPORT_SYMBOL_GPL(relay_flush);
>  static int relay_file_open(struct inode *inode, struct file *filp)
>  {
>  	struct rchan_buf *buf = inode->i_private;
> +	if (unlikely(buf == NULL))
> +		return -ENOENT;
> +
>  	kref_get(&buf->kref);
>  	filp->private_data = buf;

If it can go away before open is called, what prevents it from going
away after that check but before kref_get() is called?

-- 
Jens Axboe



      reply	other threads:[~2022-09-08 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 21:17 Yichun Zhang (agentzh)
2022-09-08 21:19 ` Jens Axboe [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=995450c5-a4f2-d2d1-8a44-569726eb7231@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=akpm@linux-foundation.org \
    --cc=colin.i.king@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yichun@openresty.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®