From: Qian Cai <quic_qiancai@quicinc.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <catalin.marinas@arm.com>,
<dvyukov@google.com>, <peterz@infradead.org>,
<valentin.schneider@arm.com>, <will@kernel.org>,
<woodylin@google.com>
Subject: Re: [PATCH] Reset task stack state in bringup_cpu()
Date: Wed, 17 Nov 2021 18:39:19 -0500 [thread overview]
Message-ID: <YZWSpz75zMms133n@fixkernel.com> (raw)
In-Reply-To: <20211117115234.GB41542@C02TD0UTHF1T.local>
On Wed, Nov 17, 2021 at 11:52:34AM +0000, Mark Rutland wrote:
> > Thanks for fixing this quickly, Mark. Triggering an user-after-free in
> > user namespace but don't think it is related. I'll investigate that
> > first since it is blocking the rest of regression testing.
>
> Cool; are you happy to provide a Tested-by tag for this patch? :)
Sure, the testing is running good so far.
Tested-by: Qian Cai <quic_qiancai@quicinc.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Qian Cai <quic_qiancai@quicinc.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <catalin.marinas@arm.com>,
<dvyukov@google.com>, <peterz@infradead.org>,
<valentin.schneider@arm.com>, <will@kernel.org>,
<woodylin@google.com>
Subject: Re: [PATCH] Reset task stack state in bringup_cpu()
Date: Wed, 17 Nov 2021 18:39:19 -0500 [thread overview]
Message-ID: <YZWSpz75zMms133n@fixkernel.com> (raw)
In-Reply-To: <20211117115234.GB41542@C02TD0UTHF1T.local>
On Wed, Nov 17, 2021 at 11:52:34AM +0000, Mark Rutland wrote:
> > Thanks for fixing this quickly, Mark. Triggering an user-after-free in
> > user namespace but don't think it is related. I'll investigate that
> > first since it is blocking the rest of regression testing.
>
> Cool; are you happy to provide a Tested-by tag for this patch? :)
Sure, the testing is running good so far.
Tested-by: Qian Cai <quic_qiancai@quicinc.com>
next prev parent reply other threads:[~2021-11-17 23:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 11:33 [PATCH] Reset task stack state in bringup_cpu() Mark Rutland
2021-11-15 11:33 ` Mark Rutland
2021-11-15 12:16 ` Valentin Schneider
2021-11-15 12:16 ` Valentin Schneider
2021-11-15 14:09 ` Mark Rutland
2021-11-15 14:09 ` Mark Rutland
2021-11-15 18:16 ` Mark Rutland
2021-11-15 18:16 ` Mark Rutland
2021-11-16 16:31 ` Qian Cai
2021-11-16 16:31 ` Qian Cai
2021-11-17 11:52 ` Mark Rutland
2021-11-17 11:52 ` Mark Rutland
2021-11-17 23:39 ` Qian Cai [this message]
2021-11-17 23:39 ` Qian Cai
2023-03-11 10:52 ` David Woodhouse
2023-03-11 10:52 ` David Woodhouse
2023-03-11 10:52 ` David Woodhouse
2023-03-11 20:29 ` Johannes Berg
2023-03-11 20:29 ` Johannes Berg
2023-03-11 20:29 ` Johannes Berg
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=YZWSpz75zMms133n@fixkernel.com \
--to=quic_qiancai@quicinc.com \
--cc=catalin.marinas@arm.com \
--cc=dvyukov@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--cc=will@kernel.org \
--cc=woodylin@google.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.