On 11/22/18 7:06 AM, Einarsson, Jim wrote:
Saul, We have no objections to your investigation of a kernel up version, but the forklift may be heavier than you realize. Certainly considerable work needs to be done to validate both functionality and performance aspects. I assume the investigation will happen in a sandbox side stream, to avoid disruption to the main branch. I highly recommend a spec be created and reviewed, to make sure all the necessary angles of the investigation are covered.
Exactly, we need to start this work for the Clear port we are currently doing and it will also need to be done as part of the Multi-OS effort since Ubuntu has a newer kernel. I am not proposing this happen on CentOS / master at this time, we know there is a large amount of work the forklift the patches, that work is already started against the 4.19 LTS kernel internally at Intel. We will work on a spec and address testing of the kernel. Sau!
JimE.
Message: 3 Date: Wed, 21 Nov 2018 09:10:47 -0800 From: Saul Wold <sgw@linux.intel.com> To: Victor Rodriguez <vm.rod25@gmail.com>, Brent.Rowsell@windriver.com Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] Migrate Starling X kernel patches to LTS kernel Message-ID: <b2bea0e0-c0c8-e57b-91d1-00a76da9c512@linux.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed
Victor, Brent:
There are a couple of things not mentioned that I have heard talked about on both sides of this discussion.
My understanding is that the kernel version is based on the RHEL/CentOS version as it's a known tested combination at the Distro level, even though there are patches to the kernel and user-space.
On the other side, the 3.10 RHEL kernel (with all the RHEL patches) may not address all the known CVEs, so there is a concern about overall security. Intel is looking at the newer kernel and porting the StarlingX patches (as needed) for the Clear and Multi-OS parts of the project.
The overall question becomes can StarlingX take the 4.19LTS kernel as a newer base kernel for the project, it reduces the overall patch load and address some security issues.
I believe you understand these objectives.
Sau!
-----Original Message----- From: starlingx-discuss-request@lists.starlingx.io [mailto:starlingx-discuss-request@lists.starlingx.io] Sent: Wednesday, November 21, 2018 4:37 PM To: starlingx-discuss@lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 6, Issue 70
Send Starlingx-discuss mailing list submissions to starlingx-discuss@lists.starlingx.io
To subscribe or unsubscribe via the World Wide Web, visit http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request@lists.starlingx.io
You can reach the person managing the list at starlingx-discuss-owner@lists.starlingx.io
When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..."
Today's Topics:
1. StarlingX mini-PTG Jan 15-16 in Phoenix (Jones, Bruce E) 2. Re: stx-tools: document isn't aligned with code (Arevalo, Mario Alfredo C) 3. Re: Migrate Starling X kernel patches to LTS kernel (Saul Wold) 4. Re: Migrate Starling X kernel patches to LTS kernel (Rowsell, Brent) 5. [build][meetings]Agenda for Build team meeting 11/22/2018 (Lara, Cesar)
----------------------------------------------------------------------
Message: 1 Date: Wed, 21 Nov 2018 16:26:43 +0000 From: "Jones, Bruce E" <bruce.e.jones@intel.com> To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io> Subject: [Starlingx-discuss] StarlingX mini-PTG Jan 15-16 in Phoenix Message-ID: <9A85D2917C58154C960D95352B22818BB1EB0050@fmsmsx115.amr.corp.intel.com>
Content-Type: text/plain; charset="utf-8"
We are thinking about holding a StarlingX mini-PTG meeting in January in Phoenix, to be hosted on the Intel campus.
I'd like to get an early headcount and make sure there are no conflicts for the dates. Please reply to this email and let me know if you can/want to attend, or if you would like to attend but have a conflict for these dates.
Thank you!
brucej