Github messages for voidlinux
 help / color / mirror / Atom feed
From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Virtualbox DKMS fails on Linux 6.4.10
Date: Tue, 15 Aug 2023 17:16:34 +0200	[thread overview]
Message-ID: <20230815151634.CZtYfFTfqcN7UIOnat0Xtli4D7IQf5-KAeksTHaYujo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45581@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 4729 bytes --]

Closed issue by dmarto on void-packages repository

https://github.com/void-linux/void-packages/issues/45581

Description:
### Is this a new report?

Yes

### System Info

Void 6.4.8_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFFFFFFFFF

### Package(s) Affected

virtualbox-ose-dkms-7.0.10_1, linux6.4-6.4.10_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://www.virtualbox.org/ticket/21796

### Expected behaviour

Building DKMS module `virtualbox-ose-7.0.10` for `linux-6.4.10` to not fail.

### Actual behaviour

```
DKMS make.log for virtualbox-ose-7.0.10 for kernel 6.4.10_1 (x86_64)
Sun Aug 13 05:56:28 PM EEST 2023
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/linux/SUPDrv-linux.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrv.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetadp/linux/VBoxNetAdp-linux.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/VBoxNetFlt.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrvGip.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetadp/VBoxNetAdp.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrvSem.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/SUPR0IdcClient.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrvTracer.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/SUPR0IdcClientComponent.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPLibAll.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/common/string/strformatrt.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/combined-agnostic1.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/combined-agnostic2.o
  CC [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/combined-os-specific.o
  LD [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetadp/vboxnetadp.o
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrvTracer.o: warning: objtool: SUPR0TracerFireProbe+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub+0x0: 'naked' return found in RETHUNK build
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrvTracer.o: warning: objtool: SUPR0TracerFireProbe+0x7: missing int3 after indirect jump
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub+0x0: missing int3 after ret
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c: In function 'vboxNetFltLinuxForwardToIntNetInner':
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40: error: implicit declaration of function 'skb_gso_segment'; did you mean 'skb_gso_reset'? [-Werror=implicit-function-declaration]
 1570 |             struct sk_buff *pSegment = skb_gso_segment(pBuf, 0 /*supported features*/);
      |                                        ^~~~~~~~~~~~~~~
      |                                        skb_gso_reset
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.c:1570:40: warning: initialization of 'struct sk_buff *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:252: /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt/linux/VBoxNetFlt-linux.o] Error 1
make[1]: *** [scripts/Makefile.build:497: /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxnetflt] Error 2
make[1]: *** Waiting for unfinished jobs....
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: rtThreadCtxHooksLnxSchedOut+0x1f: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: rtThreadCtxHooksLnxSchedIn+0x29: call to {dynamic}() with UACCESS enabled
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: VBoxHost_RTR0MemKernelCopyFrom+0x13: redundant CLD
/var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/combined-os-specific.o: warning: objtool: VBoxHost_RTR0MemKernelCopyTo+0x13: redundant CLD
  LD [M]  /var/lib/dkms/virtualbox-ose/7.0.10/build/vboxdrv/vboxdrv.o
make: *** [Makefile:2032: /var/lib/dkms/virtualbox-ose/7.0.10/build] Error 2
```

### Steps to reproduce

1. Install latest linux6.4 pkg
2. Install `virtualbox-ose-dkms`
3. Watch logs

      reply	other threads:[~2023-08-15 15:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13 15:05 [ISSUE] " dmarto
2023-08-15 15:16 ` sgn [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=20230815151634.CZtYfFTfqcN7UIOnat0Xtli4D7IQf5-KAeksTHaYujo@z \
    --to=sgn@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).