From: Greg KH <gregkh@linuxfoundation.org>
To: George Guo <dongtai.guo@linux.dev>
Cc: tom.zanussi@linux.intel.com, stable@vger.kernel.org
Subject: Re:
Date: Tue, 23 Apr 2024 09:48:19 -0700 [thread overview]
Message-ID: <2024042313-relapse-confirm-dc7a@gregkh> (raw)
In-Reply-To: <20240419154658.4015260-1-dongtai.guo@linux.dev>
On Fri, Apr 19, 2024 at 11:46:56PM +0800, George Guo wrote:
> Subject: [PATCH 4.19.y v6 0/2] Double-free bug discovery on testing trigger-field-variable-support.tc
>
> 1) About v4-0001-tracing-Remove-hist-trigger-synth_var_refs.patch:
>
> The reason I am backporting this patch is that no one found the double-free bug
> at that time, then later the code was removed on upstream, but
> 4.19-stable has the bug.
Both now queued up, thanks
greg k-h
next prev parent reply other threads:[~2024-04-23 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 15:46 George Guo
2024-04-19 15:46 ` [PATCH 4.19.y v6 1/2] tracing: Remove hist trigger synth_var_refs George Guo
2024-04-19 15:46 ` [PATCH 4.19.y v6 2/2] tracing: Use var_refs[] for hist trigger reference checking George Guo
2024-04-23 16:48 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-13 15:48 [PATCH 6.15 000/480] 6.15.10-rc1 review Jon Hunter
2025-08-13 17:25 ` Jon Hunter
2025-08-14 15:36 ` Greg KH
2025-08-15 16:20 ` Re: Jon Hunter
2025-08-15 16:53 ` Re: Greg KH
2024-11-23 1:39 the Hide
2024-11-23 7:32 ` Christoph Biedl
2023-02-28 6:32 Re: Mahmut Akten
2022-11-09 14:34 Denis Arefev
2022-11-09 14:44 ` Greg Kroah-Hartman
2022-06-06 5:33 Fenil Jain
2022-06-06 5:51 ` Greg Kroah-Hartman
2021-01-19 0:10 David Howells
2021-01-20 14:46 ` Jarkko Sakkinen
2018-12-04 2:34 RE, Ms Sharifah Ahmad Mustahfa
2018-11-06 1:19 RE, Miss Juliet Muhammad
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=2024042313-relapse-confirm-dc7a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dongtai.guo@linux.dev \
--cc=stable@vger.kernel.org \
--cc=tom.zanussi@linux.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