From: Kees Cook <keescook@chromium.org>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>, ebiederm@xmission.com
Cc: limin <limin100@huawei.com>,
shuah@kernel.org, ebiederm@xmission.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
songmuchun@bytedance.com, lizefan.x@bytedance.com
Subject: Re: [PATCH -next] selftests/ptrace: Fix Test terminated by timeout in ptrace_attach
Date: Thu, 1 Dec 2022 16:48:20 -0800 [thread overview]
Message-ID: <202212011638.31BBB562B@keescook> (raw)
In-Reply-To: <AS8P193MB1285BCEDA342A074F6A837FDE4139@AS8P193MB1285.EURP193.PROD.OUTLOOK.COM>
On Mon, Nov 28, 2022 at 08:56:09AM +0100, Bernd Edlinger wrote:
> thanks for cleaning this up.
Oh, hm, I never saw the original email -- I'll check my Spam folder, it
gets overly excited sometimes.
> Just for completenes:
>
> I have actually two patches submitted a while ago, but did not get any response so far,
> one that would make the test case work as it is:
>
> [PATCH v10] exec: Fix dead-lock in de_thread with ptrace_attach
> https://lore.kernel.org/lkml/AM8PR10MB470801D01A0CF24BC32C25E7E40E9@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM/
>
> and my favorite one, that would fix the dead-lock altogether (and adjust the test case accordingly):
>
> [PATCH v11] exec: Fix dead-lock in de_thread with ptrace_attach
> https://lore.kernel.org/lkml/AM8PR10MB470875B22B4C08BEAEC3F77FE4169@AM8PR10MB4708.EURPRD10.PROD.OUTLOOK.COM/
This fell off my radar, but let's look at it again. Is this still an
existing race after Eric's various refactorings? I assume so. Eric, can
you looked at this case?
--
Kees Cook
next prev parent reply other threads:[~2022-12-02 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 7:04 [PATCH -next] selftests/ptrace: Fix Test terminated by timeout in ptrace_attach limin
2022-11-28 7:56 ` Bernd Edlinger
2022-12-02 0:48 ` Kees Cook [this message]
2023-07-01 14:58 ` Zheng Yejian
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=202212011638.31BBB562B@keescook \
--to=keescook@chromium.org \
--cc=bernd.edlinger@hotmail.de \
--cc=ebiederm@xmission.com \
--cc=limin100@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=shuah@kernel.org \
--cc=songmuchun@bytedance.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