public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: theflamefire89@gmail.com
To: cip-dev@lists.cip-project.org
Subject: Re: [4.4.y] cred_getsecid hook
Date: Wed, 29 Jun 2022 08:44:31 -0700	[thread overview]
Message-ID: <7356.1656517471464294518@lists.cip-project.org> (raw)
In-Reply-To: <20220622120633.GB7458@duo.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]

> 
> If CVE-2021-39686 is important to you, right way forward would be to
> backport neccessary changes to 4.9, first. We would rather not have
> changes in 4.4-st that are not present in 4.9.X.

Hi Pavel, thanks for the reply.

I'm happy to contribute what I have back to 4.9. Can you give me some guidance on how I'd do that?
I've never contributed to the upstream kernel before but am confident in C/C++ and git and am maintaining an Android kernel fork.
In this case it should be pretty straight forward. All commits are from Googles android-mainline branch, backported where required, but mostly unchanged and I have the upstream discussions from the kernel ML for reference. If you are curious the 38 commits I want to backport to reduce the divergence and then fix that CVE can be found at https://github.com/Flamefire/android_kernel_sony_msm8998/pull/24.

It will likely be easy enough to port them to the 4.9 branch but I'd need to know how to have them applied and/or who to contact.

Best Regards,
Alex

PS: Greetings from Dresden, Germany

[-- Attachment #2: Type: text/html, Size: 1231 bytes --]

  reply	other threads:[~2022-06-29 15:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 13:30 [4.4.y] cred_getsecid hook theflamefire89
2022-06-22 12:06 ` [cip-dev] " Pavel Machek
2022-06-29 15:44   ` theflamefire89 [this message]
2022-06-29 18:27     ` Pavel Machek

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=7356.1656517471464294518@lists.cip-project.org \
    --to=theflamefire89@gmail.com \
    --cc=cip-dev@lists.cip-project.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