All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: He Zhe <zhe.he@windriver.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 5.10] rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow
Date: Fri, 18 Oct 2024 16:28:55 +0200	[thread overview]
Message-ID: <2024101859-polish-hurry-bd35@gregkh> (raw)
In-Reply-To: <20241018135428.1422904-2-zhe.he@windriver.com>

On Fri, Oct 18, 2024 at 09:54:25PM +0800, He Zhe wrote:
> From: Nikita Kiryushin <kiryushin@ancud.ru>
> 
> commit cc5645fddb0ce28492b15520306d092730dffa48 upstream.

Again, this is already in a release, 5.10.226, which came out well over
a month ago.  Are you sure you tested all of these properly?  What tree
are you working against?  When was it last updated?

confused,

greg k-h

  reply	other threads:[~2024-10-18 14:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 13:54 [PATCH 5.10] gfs2: Fix potential glock use-after-free on unmount He Zhe
2024-10-18 13:54 ` [PATCH 5.10] rcu-tasks: Fix show_rcu_tasks_trace_gp_kthread buffer overflow He Zhe
2024-10-18 14:28   ` Greg KH [this message]
2024-10-18 13:54 ` [PATCH 5.10] ftrace: Fix possible use-after-free issue in ftrace_location() He Zhe
2024-10-18 14:27   ` Greg KH
2024-10-18 13:54 ` [PATCH 5.10] drm/amdkfd: don't allow mapping the MMIO HDP page with large pages He Zhe
2024-10-18 14:27   ` Greg KH
2024-10-18 13:54 ` [PATCH 5.10] watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger He Zhe
2024-10-18 14:26   ` Greg KH
2024-10-18 14:26 ` [PATCH 5.10] gfs2: Fix potential glock use-after-free on unmount Greg KH

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=2024101859-polish-hurry-bd35@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    --cc=zhe.he@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.