From: Greg KH <gregkh@linuxfoundation.org>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Has the linux-kernel already implemented the functions in apollo-kernel?
Date: Sun, 15 Nov 2020 11:21:29 +0100 [thread overview]
Message-ID: <X7EBKS5BNl8eHi9X@kroah.com> (raw)
In-Reply-To: <CAGP6POKB=dbeyGSCG2qgjZGq-wKcPBOjOLLuzeWME=Pbax7uhg@mail.gmail.com>
On Sat, Oct 31, 2020 at 02:44:07PM +0800, Hongyi Zhao wrote:
> Hi,
>
> The apollo-kernel (https://github.com/ApolloAuto/apollo-kernel) is a
> patched Linux Kernel based on official Linux Kernel 4.4.32 with some
> modifications on the kernel level, especially for the scenario
> necessary to run the Apollo (https://github.com/ApolloAuto/apollo)
> open autonomous driving platform software stack.
>
> According to the official description as shown
> <https://github.com/ApolloAuto/apollo-kernel#what-is-the-difference>,
> the major difference from the original Linux kernel is as follows:
>
>
> - Realtime patch (https://rt.wiki.kernel.org/index.php/RT_PREEMPT_HOWTO)
> - Latest e1000e intel ethernet driver
> - Bugfix for Nvidia driver under realtime patch
> - Double free in the inet_csk_clone_lock function patch
> (https://bugzilla.redhat.com/show_bug.cgi?id=1450972)
> - Other cve security patches
>
>
> However, considering that Linux Kernel 4.4.32 is a fairly old version,
> so I want to know whether the modifications/fixes applied/added have
> been already available in the current Linux kernel.
>
> Any hints will be highly appreciated.
As you have the source to both trees, why not compare them and see if
all of this is true or not? That's the best way to be sure.
good luck!
greg k-h
prev parent reply other threads:[~2020-11-15 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 6:44 Has the linux-kernel already implemented the functions in apollo-kernel? Hongyi Zhao
2020-11-15 10:21 ` Greg KH [this message]
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=X7EBKS5BNl8eHi9X@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hongyi.zhao@gmail.com \
--cc=linux-kernel@vger.kernel.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