Skip to contentSkip to conversation

Please apply 90dfeef1cd38 to 6.1 through 6.18

DISCUSSION Nathan Chancellor 2 participants 2 messages Jul 25 Stable branch

lore
Share & tools
lore
#0 lore raw

Hi stable folks,

Upstream commit cc39f3872c08 ("seqlock: Introduce scoped_seqlock_read()") was backported in several stable branches (6.18 through 6.1) recently without a necessary fix, commit 90dfeef1cd38 ("seqlock: Cure some more scoped_seqlock() optimization fails"), breaking the build for certain configurations

https://github.com/ClangBuiltLinux/linux/issues/2178

Please consider applying 90dfeef1cd38 to 6.18 through 6.1 to avoid this, it applies cleanly to all those trees for me. You may also want to consider taking

b94d45b6bbb4 ("seqlock: Allow KASAN to fail optimizing") 88331c4ec23a ("seqlock: Allow UBSAN_ALIGNMENT to fail optimizing")

but I did not test if they were clean cherry picks.

Signature · 2 lines
Cheers,
Nathan
#1 lore raw
Quoted 10 lines · Nathan Chancellor

Hi stable folks,

Upstream commit cc39f3872c08 ("seqlock: Introduce scoped_seqlock_read()") was backported in several stable branches (6.18 through 6.1) recently without a necessary fix, commit 90dfeef1cd38 ("seqlock: Cure some more scoped_seqlock() optimization fails"), breaking the build for certain configurations

https://github.com/ClangBuiltLinux/linux/issues/2178

Quoted 8 lines

Please consider applying 90dfeef1cd38 to 6.18 through 6.1 to avoid this, it applies cleanly to all those trees for me. You may also want to consider taking

b94d45b6bbb4 ("seqlock: Allow KASAN to fail optimizing") 88331c4ec23a ("seqlock: Allow UBSAN_ALIGNMENT to fail optimizing")

but I did not test if they were clean cherry picks.

they do seem clean, so I've taken them all now, thanks!

greg k-h