Dear RT Folks,
I'm pleased to announce the 5.10.30-rt37 stable release.
This release is just an update to the new stable 5.10.30 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v5.10-rt
Head SHA1: 1df1cfc1a111790bb79975f27a1bda9bc632a940
Or to build 5.10.30-rt37 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v5.x/linux-5.10.tar.xz
http://www.kernel.org/pub/linux/kernel/v5.x/patch-5.10.30.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/5.10/patch-5.10.30-rt37.patch.xz
Enjoy,
-- Steve
Hello,
I tried to compile 5.0.30-rt37 on Fedora 33 and I met the following error during compilation:
CC net/ipv4/datagram.o
In file included from ./include/linux/mmzone.h:16,
from ./include/linux/gfp.h:6,
from ./include/linux/mm.h:10,
from ./include/linux/bvec.h:14,
from ./include/linux/skbuff.h:17,
from ./include/net/xfrm.h:9,
from net/xfrm/xfrm_state.c:18:
net/xfrm/xfrm_state.c: In function 'xfrm_state_init':
./include/linux/seqlock.h:178:36: error: initialization of 'seqcount_spinlock_t *' {aka 'struct seqcount_spinlock *'} from incompatible pointer type 'seqcount_t *' {aka 'struct seqcount *'} [-Werror=incompatible-pointer-types]
178 | seqcount_##lockname##_t *____s = (s); \
| ^
./include/linux/seqlock.h:184:42: note: in expansion of macro 'seqcount_LOCKNAME_init'
184 | #define seqcount_spinlock_init(s, lock) seqcount_LOCKNAME_init(s, lock, spinlock)
| ^~~~~~~~~~~~~~~~~~~~~~
net/xfrm/xfrm_state.c:2666:2: note: in expansion of macro 'seqcount_spinlock_init'
2666 | seqcount_spinlock_init(&net->xfrm.xfrm_state_hash_generation,
| ^~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:279: net/xfrm/xfrm_state.o] Error 1
make[1]: *** [scripts/Makefile.build:496: net/xfrm] Error 2
make[1]: *** Waiting for unfinished jobs....
Best regards,
Yann
----- Mail original -----
De: "Steven Rostedt" <[email protected]>
À: "LKML" <[email protected]>, "linux-rt-users" <[email protected]>
Cc: "Thomas Gleixner" <[email protected]>, "Carsten Emde" <[email protected]>, "John Kacur" <[email protected]>, "Sebastian Andrzej Siewior" <[email protected]>, "Daniel Wagner" <[email protected]>, "Tom Zanussi" <[email protected]>, "Srivatsa S. Bhat" <[email protected]>
Envoyé: Mardi 20 Avril 2021 00:47:31
Objet: [ANNOUNCE] 5.10.30-rt37
Dear RT Folks,
I'm pleased to announce the 5.10.30-rt37 stable release.
This release is just an update to the new stable 5.10.30 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
branch: v5.10-rt
Head SHA1: 1df1cfc1a111790bb79975f27a1bda9bc632a940
Or to build 5.10.30-rt37 directly, the following patches should be applied:
http://www.kernel.org/pub/linux/kernel/v5.x/linux-5.10.tar.xz
http://www.kernel.org/pub/linux/kernel/v5.x/patch-5.10.30.xz
http://www.kernel.org/pub/linux/kernel/projects/rt/5.10/patch-5.10.30-rt37.patch.xz
Enjoy,
-- Steve
On Tue, Apr 20, 2021, [email protected] wrote:
>
> net/xfrm/xfrm_state.c: In function 'xfrm_state_init':
> ./include/linux/seqlock.h:178:36: error: initialization of 'seqcount_spinlock_t *' {aka 'struct seqcount_spinlock *'} from incompatible pointer type 'seqcount_t *' {aka 'struct seqcount *'} [-Werror=incompatible-pointer-types]
> 178 | seqcount_##lockname##_t *____s = (s); \
> | ^
...
> net/xfrm/xfrm_state.c:2666:2: note: in expansion of macro 'seqcount_spinlock_init'
> 2666 | seqcount_spinlock_init(&net->xfrm.xfrm_state_hash_generation,
> | ^~~~~~~~~~~~~~~~~~~~~~
There is a rebase error at:
247560698349 ("Merge tag 'v5.10.30' into v5.10-rt")
Cherry-pick mainline's commit:
bc8e0adff343 ("net: xfrm: Use sequence counter with associated spinlock")
and your compilation issue will be fixed.
Good luck,
--
Ahmed S. Darwish
On 4/19/2021 5:47 PM, Steven Rostedt wrote:
> On Tue, Apr 20, 2021,[email protected] wrote:
>> net/xfrm/xfrm_state.c: In function 'xfrm_state_init':
>> ./include/linux/seqlock.h:178:36: error: initialization of 'seqcount_spinlock_t *' {aka 'struct seqcount_spinlock *'} from incompatible pointer type 'seqcount_t *' {aka 'struct seqcount *'} [-Werror=incompatible-pointer-types]
>> 178 | seqcount_##lockname##_t *____s = (s); \
>> | ^
> ...
>> net/xfrm/xfrm_state.c:2666:2: note: in expansion of macro 'seqcount_spinlock_init'
>> 2666 | seqcount_spinlock_init(&net->xfrm.xfrm_state_hash_generation,
>> | ^~~~~~~~~~~~~~~~~~~~~~
> There is a rebase error at:
>
> 247560698349 ("Merge tag 'v5.10.30' into v5.10-rt")
>
> Cherry-pick mainline's commit:
>
> bc8e0adff343 ("net: xfrm: Use sequence counter with associated spinlock")
Thanks for this fix, Cherry-pick resolved rt stable integration issue
that i was seeing.
Is this fix going to be posted for v5.10-rt too ?
>
> and your compilation issue will be fixed.
On Mon, 3 May 2021 15:39:19 -0500
"Bajjuri, Praneeth" <[email protected]> wrote:
> On 4/19/2021 5:47 PM, Steven Rostedt wrote:
> > On Tue, Apr 20, 2021,[email protected] wrote:
> >> net/xfrm/xfrm_state.c: In function 'xfrm_state_init':
> >> ./include/linux/seqlock.h:178:36: error: initialization of 'seqcount_spinlock_t *' {aka 'struct seqcount_spinlock *'} from incompatible pointer type 'seqcount_t *' {aka 'struct seqcount *'} [-Werror=incompatible-pointer-types]
> >> 178 | seqcount_##lockname##_t *____s = (s); \
> >> | ^
> > ...
> >> net/xfrm/xfrm_state.c:2666:2: note: in expansion of macro 'seqcount_spinlock_init'
> >> 2666 | seqcount_spinlock_init(&net->xfrm.xfrm_state_hash_generation,
> >> | ^~~~~~~~~~~~~~~~~~~~~~
> > There is a rebase error at:
> >
> > 247560698349 ("Merge tag 'v5.10.30' into v5.10-rt")
> >
> > Cherry-pick mainline's commit:
> >
> > bc8e0adff343 ("net: xfrm: Use sequence counter with associated spinlock")
>
> Thanks for this fix, Cherry-pick resolved rt stable integration issue
> that i was seeing.
>
> Is this fix going to be posted for v5.10-rt too ?
>
> >
> > and your compilation issue will be fixed.
Yes, I'm pulling it in now (sorry for the delay).
For some reason, Yann's email never made it into my INBOX :-/
But cherry picking that commit appears to do the job. I'll pull that in,
and then start bringing 5.10 to the latest release.
-- Steve