From: Ronald Warsow <rwarsow@gmx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.4 000/165] 6.4.10-rc1 review
Date: Wed, 9 Aug 2023 15:40:48 +0200 [thread overview]
Message-ID: <5bba262f-c3a4-fdc0-deff-da3cb0dc49e4@gmx.de> (raw)
Hi Greg
6.4.10-rc1
compiles [1], boots and runs here on x86_64
(Intel Rocket Lake, i5-11400)
[1]
But I'm unable to compile vbox external modules anymore
seems to be a regression against Kernel 6.4.9
- WERROR is not set
- GDS_FORCE_MITIGATION=y
- new microcode is on the box
Error Message
=============
...
/tmp/vbox.0/linux/VBoxNetFlt-linux.c: In function
‘vboxNetFltLinuxForwardToIntNetInner’:
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:1570:40: error: implicit
declaration of function ‘skb_gso_segment’; did you mean ‘skb_gso_reset’?
[-Werror=implicit-functio
n-declaration]
1570 | struct sk_buff *pSegment = skb_gso_segment(pBuf, 0
/*supported features*/);
| ^~~~~~~~~~~~~~~
| skb_gso_reset
/tmp/vbox.0/linux/VBoxNetFlt-linux.c:1570:40: warning: initialization of
‘struct sk_buff *’ from ‘int’ makes pointer from integer without a cast
[-Wint-conversi
on]
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:252:
/tmp/vbox.0/linux/VBoxNetFlt-linux.o] Error 1
make[1]: *** [Makefile:2032: /tmp/vbox.0] Error 2
make: *** [/tmp/vbox.0/Makefile-footer.gmk:133: vboxnetflt] Error 2
Thanks
Tested-by: Ronald Warsow <rwarsow@gmx.de>
next reply other threads:[~2023-08-09 13:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:40 Ronald Warsow [this message]
2023-08-11 14:16 ` Greg Kroah-Hartman
2023-08-11 15:48 ` Ronald Warsow
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 10:38 Greg Kroah-Hartman
2023-08-09 13:43 ` Joel Fernandes
2023-08-09 15:51 ` Justin Forbes
2023-08-09 17:11 ` SeongJae Park
2023-08-09 21:20 ` Ron Economos
2023-08-09 22:23 ` Florian Fainelli
2023-08-10 4:11 ` Bagas Sanjaya
2023-08-10 10:30 ` Conor Dooley
2023-08-10 16:15 ` Guenter Roeck
2023-08-10 21:21 ` Miguel Ojeda
2023-08-11 3:25 ` Naresh Kamboju
2023-08-14 14:15 ` Thierry Reding
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=5bba262f-c3a4-fdc0-deff-da3cb0dc49e4@gmx.de \
--to=rwarsow@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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
all inboxes | Powered by JetHome®