Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linux-kernel-latest v5.2.3-1 (r4.0) #1239

Closed
qubesos-bot opened this issue Jul 28, 2019 · 5 comments
Closed

linux-kernel-latest v5.2.3-1 (r4.0) #1239

qubesos-bot opened this issue Jul 28, 2019 · 5 comments

Comments

@qubesos-bot
Copy link

Update of linux-kernel-latest to v5.2.3-1 for Qubes r4.0, see comments below for details.

Built from: QubesOS/qubes-linux-kernel@d9f5315

Changes since previous version:
QubesOS/qubes-linux-kernel@d9f5315 Drop AFTER_LINK patch
QubesOS/qubes-linux-kernel@150288e Update to kernel-5.2.3
QubesOS/qubes-linux-kernel@9ec4071 Update WireGuard to 0.0.20190702

Referenced issues:

If you're release manager, you can issue GPG-inline signed command:

  • Upload linux-kernel-latest d9f5315adac43fce54a01cc65226c4de9b4b680b r4.0 current repo (available 7 days from now)
  • Upload linux-kernel-latest d9f5315adac43fce54a01cc65226c4de9b4b680b r4.0 current (dists) repo, you can choose subset of distributions, like vm-fc24 vm-fc25 (available 7 days from now)
  • Upload linux-kernel-latest d9f5315adac43fce54a01cc65226c4de9b4b680b r4.0 security-testing repo

Above commands will work only if packages in current-testing repository were built from given commit (i.e. no new version superseded it).

@qubesos-bot
Copy link
Author

Package for dom0 was built (build log) and uploaded to current-testing repository

@marmarek
Copy link
Member

@marmarek marmarek added the buggy label Jul 28, 2019
@m-v-b
Copy link

m-v-b commented Jul 28, 2019

Hello @marmarek and @fepitre,

I debugged this issue a bit, and I currently think that this issue is related to the following commit introduced with Linux v5.2: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=df9bde015a72ffd978e39a750662c7cf579b1715

How did I arrive at this conclusion? In summary, the libxenvchan_client_init function fails due to the inability to mmap the /dev/xen/gntdev device node, which causes qubes-db daemon initialization to fail, breaking AppVM bootstrap. I think that the aforementioned commit unintendedly changed/broke the behaviour of the code, but I did not confirm this yet, so this is only a guess for now.

To confirm my guess, I am in the process of building a kernel with this commit reverted, and I will report back with my findings after testing the kernel I am building.

I hope that this helps!

Vefa

@marmarek
Copy link
Member

Thanks!
I'm looking at it right now and I have similar conclusion for now (not verified yet).
Lets track it with a proper issue: QubesOS/qubes-issues#5199

@marmarek
Copy link
Member

Superseded by #1268

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants