Skip to content
This repository was archived by the owner on May 12, 2021. It is now read-only.

v4.19.52: patch and config update for v4.19.52 on AArch64#592

Merged
gnawux merged 1 commit intokata-containers:masterfrom
Pennyzct:v4.19.52
Jun 21, 2019
Merged

v4.19.52: patch and config update for v4.19.52 on AArch64#592
gnawux merged 1 commit intokata-containers:masterfrom
Pennyzct:v4.19.52

Conversation

@Pennyzct
Copy link
Copy Markdown
Contributor

Hi~ @egernst I have already done patch and config update for v4.19.52 on AArch64.

@Pennyzct
Copy link
Copy Markdown
Contributor Author

@gnawux @egernst soooooo desperately looking forward to bump to v5.0.x. ;)

Copy link
Copy Markdown
Contributor

@grahamwhaley grahamwhaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

presuming HOTPLUG additions are deliberate,
lgtm

# CONFIG_ACPI_DEBUG is not set
# CONFIG_ACPI_PCI_SLOT is not set
CONFIG_ACPI_CONTAINER=y
CONFIG_ACPI_HOTPLUG_MEMORY=y
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I presume the HOTPLUG additions are deliberate. May want to add a note to the commit message, as they look like not just part of an update, but are an addition.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep, you just got me😱. I may need to split that to another commit...🤠

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are several entries added in this patch. Do you have any explanation here @Pennyzct?

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 20, 2019

I could understand your feeling 🤔

I prefer to stick on 4.19 before next LTS kernel is released, however, I don't mind aarch64 have a different kernel version.

@Pennyzct
Copy link
Copy Markdown
Contributor Author

@gnawux just imaging keep refining this whole big patch. it's killing me. dose everyone on board for AArch64 has different kernel version?? @egernst @jodh-intel @devimc @grahamwhaley

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 20, 2019

@Pennyzct

dose everyone on board for AArch64 has different kernel version??

I think this idea is a double-sword for you. It may help you avoid pick huge patches from non-LTS kernels, on the other hand, it might make others less care of ARM arch by some means.

I can't tell if it is a better choice for you.

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 20, 2019

@grahamwhaley could we set this PR as a dependency of CI of kata-containers/runtime#1817?

@Pennyzct
Copy link
Copy Markdown
Contributor Author

@gnawux emmmmmmm, But I have memory hot-remove, DAX, cpu hotplug, kvm-ptp on the way. 😱🙃

@grahamwhaley
Copy link
Copy Markdown
Contributor

@gnawux @egernst soooooo desperately looking forward to bump to v5.0.x. ;)

Well, there was a PR for that kata-containers/runtime#1504 , but it got closed very recently due to 'inactivity', which maybe was not the right course of action.
It got stalled as the kernel fragment PR got stuck on:

  • it seemed to make the firecracker CI less stable
  • it really should have SRIOV support added in

Personally, I suspect the right path is to move to v5.x kernels with full config files, and carry on with the fragment support work in parallel - unless there is a focussed effort to land the fragment work rsn.

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 20, 2019

emmmmmmm, But I have memory hot-remove, DAX, cpu hotplug, kvm-ptp on the way. 😱🙃

@Pennyzct awesome, how about co-present a topic on OpenInfra Summit Shanghai this November on your excellent upstream work.

@jcvenegas
Copy link
Copy Markdown
Member

/test

@jcvenegas
Copy link
Copy Markdown
Member

@Pennyzct could you add a depens on kata-containers/runtime#1817

@jcvenegas
Copy link
Copy Markdown
Member

@egernst could you add a depends-on #592 ?

egernst pushed a commit to egernst/runtime that referenced this pull request Jun 20, 2019
Update to newer stable kernel

Fixes: kata-containers#1816
Depends-on: kata-containers/packaging#592

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
egernst pushed a commit to egernst/runtime that referenced this pull request Jun 20, 2019
Update to newer stable kernel

Fixes: kata-containers#1816
Depends-on: github.com/kata-containers/packaging#592

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
egernst pushed a commit to egernst/runtime that referenced this pull request Jun 21, 2019
Update to newer stable kernel

Fixes: kata-containers#1816
Depends-on: github.com/kata-containers/packaging#592

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
@Pennyzct
Copy link
Copy Markdown
Contributor Author

Hi~ @bergwolf @jcvenegas I have already added depends-on. ;)

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 21, 2019

/test

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 21, 2019

/retest

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 21, 2019

checked the failure in the ARM test of kata-containers/runtime#1817, it is caused by lacking ptp0 device, however, looks the fix in kata-containers/osbuilder#265 won't be merged soon.

Let's merge this and kata-containers/runtime#1817 once the essential CIs are passed because this is a security related fix.

Copy link
Copy Markdown
Member

@gnawux gnawux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Pennyzct for rebasing the patch

@bergwolf
Copy link
Copy Markdown
Member

CI failed at ERROR: Please bump version in kernel/kata_config_version. @Pennyzct please bump kata_config_version.

@Pennyzct
Copy link
Copy Markdown
Contributor Author

Hi~ @bergwolf while you are on children-happy hour, I have done the update. ;)

@Pennyzct
Copy link
Copy Markdown
Contributor Author

Hi~ @grahamwhaley I'm too lazy to split a new one, I'm guilty😈, I just address HOTPLUG additions on this commit

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 21, 2019

/test

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 21, 2019

again

ERROR: Please bump version in kernel/kata_config_version

we need to do patch and config update for v4.19.52 on AArch64.
The config file adds a few configs involved with memory hot-plug
support.

Fixes: kata-containers#591
Depends-on: github.com/kata-containers/runtime#1817

Signed-off-by: Penny Zheng <penny.zheng@arm.com>
@Pennyzct
Copy link
Copy Markdown
Contributor Author

/test

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 21, 2019

finally passed, merge it

@gnawux gnawux merged commit fdacac9 into kata-containers:master Jun 21, 2019
bergwolf pushed a commit to bergwolf/kata-runtime that referenced this pull request Jun 21, 2019
Update to newer stable kernel

Fixes: kata-containers#1816
Depends-on: github.com/kata-containers/packaging#592

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
bergwolf pushed a commit to bergwolf/kata-runtime that referenced this pull request Jun 21, 2019
Update to newer stable kernel

Fixes: kata-containers#1816
Depends-on: github.com/kata-containers/packaging#592

Signed-off-by: Eric Ernst <eric.ernst@intel.com>
@bergwolf
Copy link
Copy Markdown
Member

Thanks @Pennyzct!

@devimc
Copy link
Copy Markdown

devimc commented Jun 21, 2019

@gnawux snap-ci was failing and you didn't care about it and merged this anyway!!! 👎

I can't release the new snap because it's broken, Thanks @gnawux nice job!! 👎

@jodh-intel
Copy link
Copy Markdown

@devimc, @gnawux - Relax guys 😎 Mistakes happen. Nobody got hurt right?

I think we need to all focus on fixing the CI's so that a failure is a very unusual occurrence (/me looks sideways at kata-containers/osbuilder#265 as that is causing constant failures .... ;)

But for now, can we take a deep breath, count to 10 and think about what we can do to fix this?

@jodh-intel
Copy link
Copy Markdown

@Pennyzct - do you have any calming emojis you can drop over here? 😉

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 22, 2019

@devimc,

Penny explained the snap-ci situation for me -- the snap-ci download the old kernel and will always fail for the PR. On the other hand, the 4.19.52 is a security update for a couple of CVEs, we can't wait for fixing all CIs. For a security update, we should merge it once it got enough +1 and all the required CI passed.

On the other hand, one +1 is from me. My thoughts on it: I don't think this patch broke any existing stuff

  • Firstly, this is an arch specific update, and it won't affect other archs.
  • Secondly, the aarch64 developer Penny confirmed it worked and didn't break more cases on either packaging tests and runtime CIs.

Finally, as James stated, the only failed aarch64 case in runtime repo is the chrony one, we should solve that soon.

Have a good weekend.

@Pennyzct
Copy link
Copy Markdown
Contributor Author

Hi~
@jodh-intel 🍨🍧🍦 ice-cream is always the best option here.
the fault comes from my huge, obnoxious kernel patches😡🤬, people are asking for 4.19.52, which is a security update for a couple of CVEs. So i raised this PR to do a little, tiny twist for the changing from 4.19.28 to 4.19.52.
@devimc FWIT, kernel version for snap stays in v1.8.0-alpha0, which is still the old 4.19.28. Soooooo, o(TヘTo)
I think we could include eric's kernel update PR runtime/1817 into a kata new version, maybe v1.8.0-alpha4. and update snap to this version v1.8.0-alpha4, and it will get fixed. ;)

@jodh-intel
Copy link
Copy Markdown

Thanks @Pennyzct - 🍨 sounds great, particularly with 🍒 and 🍫 on top ;)

Let's also add 🎵, a ⛲, 🌞, 😎 and some relaxing 🐟 to watch 😄

Your plan sounds good to me - wdyt @egernst?

@gnawux
Copy link
Copy Markdown
Member

gnawux commented Jun 26, 2019

@bergwolf Do as what @Pennyzct said?

I think we could include eric's kernel update PR runtime/1817 into a kata new version, maybe v1.8.0-alpha4. and update snap to this version v1.8.0-alpha4, and it will get fixed. ;)

@bergwolf
Copy link
Copy Markdown
Member

@gnawux Yeah, now that all the kernel update PRs are merged, let's roll out a series of new releases.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants