From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Ariel Miculas <ariel.miculas@gmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Fwd: [PATCH] powerpc/ptrace: Fix buffer overflow when handling PTRACE_PEEKUSER and PTRACE_POKEUSER
Date: Wed, 27 Sep 2023 16:01:57 +0000 [thread overview]
Message-ID: <9afcdb29-db22-3f5c-b596-da7567b707ff@csgroup.eu> (raw)
In-Reply-To: <CAPDJoNvADrCj8L2RAthXVbBxMNrjbY_4pnHu0QtKKARgyoQ-QA@mail.gmail.com>
Le 27/09/2023 à 17:27, Ariel Miculas a écrit :
> I've forwarded this old email thread for visibility and discussion's
> sake around my recent blog post [1][2]
Ah, right, it's been superseded by
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220609133245.573565-1-mpe@ellerman.id.au/
So I mark the new one superseded as well.
By the way, is your other patch still applicable, ref
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220610102821.252729-1-ariel.miculas@belden.com/
?
Thanks
Christophe
>
> Regards,
> Ariel
>
> [1] https://news.ycombinator.com/item?id=37671991
> [2] https://www.reddit.com/r/programming/comments/16tf5ne/how_i_got_robbed_of_my_first_kernel_contribution/?ref=share&ref_source=link
next prev parent reply other threads:[~2023-09-27 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPDJoNtU9Vuh87PxDkxo+7M_Kg_K4PPNGksPuW_guFbChYu-jA@mail.gmail.com>
[not found] ` <20220601155702.176588-1-ariel.miculas@gmail.com>
[not found] ` <CAPDJoNvZmeeU+T94rp8BJ0+bH5pDXQCEKPHiQF0Kcu=JrRRfrg@mail.gmail.com>
[not found] ` <CAPDJoNsb-HtfOQhD6ntZ8Hqx3fv3WAh1U5Jd3GzyN5EwO8znWA@mail.gmail.com>
2023-09-27 10:13 ` Fwd: [PATCH] powerpc/ptrace: Fix buffer overflow when handling PTRACE_PEEKUSER and PTRACE_POKEUSER Ariel Miculas
2023-09-27 13:38 ` Christophe Leroy
2023-09-27 15:27 ` Ariel Miculas
2023-09-27 16:01 ` Christophe Leroy [this message]
2023-09-27 19:35 ` Ariel Miculas
2023-09-28 0:53 ` Michael Ellerman
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=9afcdb29-db22-3f5c-b596-da7567b707ff@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=ariel.miculas@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).