From: Steven Rostedt <rostedt@goodmis.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: James Wang <jnwang@linux.alibaba.com>,
Liangyan <liangyan.peng@linux.alibaba.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Xunlei Pang <xlpang@linux.alibaba.com>,
yinbinbin@alibabacloud.com, wetp <wetp.zy@linux.alibaba.com>,
stable <stable@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] tracing: Correct the length check which causes memory corruption
Date: Wed, 9 Jun 2021 17:11:39 -0400 [thread overview]
Message-ID: <20210609171139.3fa05337@oasis.local.home> (raw)
In-Reply-To: <CAHk-=win1FaZQga_XYSkRLx0-mF6dSm-HhP2RQ9ZZ3S380SeOg@mail.gmail.com>
On Wed, 9 Jun 2021 13:55:04 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> I think the cleanups could be separate. I in no way _hate_ Liangyan's
> patch, it's just that when looking at it I just went "that code is
> very confusing".
OK, I'll do the clean up now for the next merge window.
>
> So I'm certainly also ok with just getting that ugly fix, and then
> hope for a cleanup later. Maybe with a comment or two.
My tests are currently at the "allyesconfig" portion, and has other
tests to finish up after that. So I expect it will be done in a few
hours, and if there's no issues, I'll send it to you after it is
completed.
Thanks,
-- Steve
next prev parent reply other threads:[~2021-06-09 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 12:57 [PATCH] tracing: Correct the length check which causes memory corruption Liangyan
2021-06-07 13:46 ` James Wang
2021-06-09 20:08 ` Linus Torvalds
2021-06-09 20:51 ` Steven Rostedt
2021-06-09 20:55 ` Linus Torvalds
2021-06-09 21:11 ` Steven Rostedt [this message]
2021-06-09 21:43 ` Linus Torvalds
2021-06-09 22:18 ` Steven Rostedt
2021-06-07 15:34 ` Steven Rostedt
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=20210609171139.3fa05337@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=gregkh@linuxfoundation.org \
--cc=jnwang@linux.alibaba.com \
--cc=liangyan.peng@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wetp.zy@linux.alibaba.com \
--cc=xlpang@linux.alibaba.com \
--cc=yinbinbin@alibabacloud.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