I tried to build linux kernel by emerging >=git-sources-6.3-rc1 and I saw an error message: assignment of read-only member ‘vm_flags’ in two points within specific source code file named, /var/tmp/portage/app-emulation/virtualbox-modules-7.0.6/work/vboxdrv/r0drv/linux/memobj-r0drv-linux.c Reproducible: Always Steps to Reproduce: 1. build kernel which version is newer or the same with 6.3-rc1 2. build a latest version of app-emulation/virtualbox-modules 3. look an error message points two line. Actual Results: error occurred from two lines of specific file. Expected Results: There should not be an error message. I will submit a patch and modified ebuild, so please review.
Created attachment 859338 [details] This file describes information of emerge settings. emerge --info
Created attachment 859349 [details] build.log of =app-emulation/virtualbox-modules-7.0.6 with >=sys-kernel/git-sources-6.3-rc1
Created attachment 859350 [details, diff] patch for =app-emulation/virtualbox-modules-7.0.6 would better to be applied if it is about to be built with >=linux-6.3-rc1
Created attachment 859351 [details] ebuild file containing an additional "PATCHES" variable
Created attachment 859453 [details, diff] vboxdrv_kernel_6.3.x.patch The upstream patch looks slightly different: https://www.virtualbox.org/changeset/98867/vbox I took that and only changed the paths to use in Gentoo. You can also use it as user patch in /etc/portage/patches/app-emulation/virtualbox-modules/ Applies for app-emulation/virtualbox-modules-7.0.6 without issues.
(In reply to jospezial from comment #5) > Created attachment 859453 [details, diff] [details, diff] > vboxdrv_kernel_6.3.x.patch > > The upstream patch looks slightly different: > https://www.virtualbox.org/changeset/98867/vbox > > I took that and only changed the paths to use in Gentoo. > You can also use it as user patch in > /etc/portage/patches/app-emulation/virtualbox-modules/ > Applies for app-emulation/virtualbox-modules-7.0.6 without issues. I reviewed again changelog that i mentioned in code, +static inline void vm_flags_set(struct vm_area_struct *vma, + vm_flags_t flags) +{ + mmap_assert_write_locked(vma->vm_mm); + ACCESS_PRIVATE(vma, __vm_flags) |= flags; +} therefore, upstream code looks more efficient. I love that. that should be applied as soon as possible. I will close this issue.
Please don't close it yet. I'll add the patch to the tree. I don't have kernel 6.3 yet, so I can't test it, I only tested it compiles with the current kernel.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=16f171d9bbc6820a7e417ec75413fe4c2bc631d1 commit 16f171d9bbc6820a7e417ec75413fe4c2bc631d1 Author: Viorel Munteanu <ceamac@gentoo.org> AuthorDate: 2023-04-03 06:11:57 +0000 Commit: Viorel Munteanu <ceamac@gentoo.org> CommitDate: 2023-04-03 06:12:43 +0000 app-emulation/virtualbox-modules: fix compilation with kernel 6.3 Bug: https://bugs.gentoo.org/903638 Signed-off-by: Viorel Munteanu <ceamac@gentoo.org> .../virtualbox-modules-7.0.6-kernel-6.3.patch | 27 ++++++++++ .../virtualbox-modules-6.1.42-r1.ebuild | 61 ++++++++++++++++++++++ .../virtualbox-modules-7.0.6-r1.ebuild | 61 ++++++++++++++++++++++ 3 files changed, 149 insertions(+)
Why revbump?
Because it's stable. I don't like to change stable ebuilds, even when it looks safe. And app-emulation/virtualbox-modules compiles quite fast, so a needless rebuild is not that costly.
7.0.6 compiles with this patch for 6.3.0 kernel. I have not yet booted into 6.3.0 so I haven't tested it running yet.
(In reply to Jack from comment #11) > 7.0.6 compiles with this patch for 6.3.0 kernel. I have not yet booted into > 6.3.0 so I haven't tested it running yet. Thank you for checking. Please find another bug not yet patched.
