Bug#943425: Debian #943425: [s390x] setjmp/longjmp do not save/restore all registers in use
Dixi quod… >Jessica Clarke brought out docs saying f8‥f15 must be saved, the >other FPU registers not: This needs to be fixed in klibc. >>• klibc does not really support the FPU anyway > >… GCC chooses to allocate an FPU register for a pointer value. This is a curiosity. >>• the half of v10 that equals f10 just HAPPENS to be saved by >> glibc, but what if the upper half, that is outside of the FPU, >> is used? > >The question here is, does GCC only use the halves of the half >of the vector registers that match the FPU registers? 04:41⎜«jrtc27:#debian-x32» hephaistor: re s390x vector registers, reading the gcc and llvm sources they're ⎜all call-clobbered by default, only the float parts are call-saved 04:41⎜«jrtc27:#debian-x32» so that's why setjmp/longjmp don't need to save/restore them 04:42⎜«jrtc27:#debian-x32» there *is* a vector calling convention, but it's not the default for the ABI, ⎜it's opt-in, and setjmp/longjmp won't be annotated as such So we indeed need to only save the registers glibc does. >@klibc list: as indicated earlier, I can provide a patch if needed >(though it should be obvious). bye, //mirabilos -- [00:02] gecko: benutzt du emacs ? [00:03] nö [00:03] nur n normalen mac [00:04] argl [00:04] ne den editor -- Vutral und gecko2 in #deutsch (NB: Editor? Betriebssystem.)
Bug#922666: confirmed bug report
Another thing I should mention is that I accidentally (I swear) ended up in memtest86 during some kernel switching tests, and figured I would let that run. It found about a dozen errors in 10-20 minutes testing, so there's also that: it could be a problem with the RAM. That said, those are new modules I got on this laptop, and the problem was happening before those were changed...
Processed: Re: Bug#988044: linux-image-5.10.0-0.bpo.4-amd64: Kernel panic due nfsd error: refcount_t: addition on 0; use-after-free
Processing control commands: > tags -1 + moreinfo Bug #988044 [src:linux] linux-image-5.10.0-0.bpo.4-amd64: Kernel panic due nfsd error: refcount_t: addition on 0; use-after-free Added tag(s) moreinfo. -- 988044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988044: linux-image-5.10.0-0.bpo.4-amd64: Kernel panic due nfsd error: refcount_t: addition on 0; use-after-free
Control: tags -1 + moreinfo Hi Olivier, On Tue, May 04, 2021 at 10:01:17AM +0200, Olivier Monaco wrote: > Package: src:linux > Version: 5.10.19-1~bpo10+1 > Severity: important > > On a virtual machine running a NFS server the following kernel panic occurs: > 2021-05-04T02:28:21.051193+02:00 storage-t20 kernel: [1736623.921391] > [ cut here ] > 2021-05-04T02:28:21.051214+02:00 storage-t20 kernel: [1736623.921406] > refcount_t: addition on 0; use-after-free. > 2021-05-04T02:28:21.051215+02:00 storage-t20 kernel: [1736623.921416] > WARNING: CPU: 0 PID: 675 at lib/refcount.c:25 refcount_warn_saturate+0x6d/0xf0 > 2021-05-04T02:28:21.051216+02:00 storage-t20 kernel: [1736623.921417] Modules > linked in: binfmt_misc vsock_loopback vmw_vsock_virtio_transport_common > vmw_vsock_vmci_transport vsock intel_rapl_msr intel_rapl_common nfit > libnvdimm crc32_pclmul ghash_clmulni_intel aesni_intel libaes crypto_simd > cryptd glue_helper rapl vm > w_balloon vmwgfx joydev evdev serio_raw pcspkr ttm sg drm_kms_helper vmw_vmci > cec ac button nfsd auth_rpcgss nfs_acl lockd grace drm sunrpc fuse configfs > ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c > crc32c_generic dm_mod sd_mod t10_pi crc_t10dif crct10dif_generic ata_generic > crct10dif_pclmul > crct10dif_common crc32c_intel psmouse vmxnet3 ata_piix libata vmw_pvscsi > scsi_mod i2c_piix4 > 2021-05-04T02:28:21.051217+02:00 storage-t20 kernel: [1736623.921488] CPU: 0 > PID: 675 Comm: nfsd Not tainted 5.10.0-0.bpo.4-amd64 #1 Debian > 5.10.19-1~bpo10+1 > 2021-05-04T02:28:21.051218+02:00 storage-t20 kernel: [1736623.921488] > Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference > Platform, BIOS 6.00 12/12/2018 > 2021-05-04T02:28:21.051219+02:00 storage-t20 kernel: [1736623.921491] RIP: > 0010:refcount_warn_saturate+0x6d/0xf0 > 2021-05-04T02:28:21.051219+02:00 storage-t20 kernel: [1736623.921492] Code: > 05 d8 be 3f 01 01 e8 c3 0a 40 00 0f 0b c3 80 3d c8 be 3f 01 00 75 ce 48 c7 c7 > 30 6c 92 86 c6 05 b8 be 3f 01 01 e8 a4 0a 40 00 <0f> 0b c3 80 3d ab be 3f 01 > 00 75 af 48 c7 c7 08 6c 92 86 c6 05 9b > 2021-05-04T02:28:21.051220+02:00 storage-t20 kernel: [1736623.921493] RSP: > 0018:b93f412b3c28 EFLAGS: 00010282 > 2021-05-04T02:28:21.051234+02:00 storage-t20 kernel: [1736623.921494] RAX: > RBX: 9c2c913a0f80 RCX: 0027 > 2021-05-04T02:28:21.051236+02:00 storage-t20 kernel: [1736623.921495] RDX: > 0027 RSI: 9c2d39e18a00 RDI: 9c2d39e18a08 > 2021-05-04T02:28:21.051237+02:00 storage-t20 kernel: [1736623.921495] RBP: > 9c2c96e4f2a4 R08: R09: c0007fff > 2021-05-04T02:28:21.051238+02:00 storage-t20 kernel: [1736623.921496] R10: > 0001 R11: b93f412b3a30 R12: 9c2c96e4f2a0 > 2021-05-04T02:28:21.051238+02:00 storage-t20 kernel: [1736623.921496] R13: > 9c2c375f5450 R14: 9c2cb4f9fde8 R15: 86f75300 > 2021-05-04T02:28:21.051244+02:00 storage-t20 kernel: [1736623.921497] FS: > () GS:9c2d39e0() knlGS: > 2021-05-04T02:28:21.051245+02:00 storage-t20 kernel: [1736623.921498] CS: > 0010 DS: ES: CR0: 80050033 > 2021-05-04T02:28:21.051245+02:00 storage-t20 kernel: [1736623.921499] CR2: > 7f424807d5b9 CR3: 000103084001 CR4: 007706f0 > 2021-05-04T02:28:21.051246+02:00 storage-t20 kernel: [1736623.921522] PKRU: > 5554 > 2021-05-04T02:28:21.051246+02:00 storage-t20 kernel: [1736623.921523] Call > Trace: > 2021-05-04T02:28:21.051246+02:00 storage-t20 kernel: [1736623.921546] > nfsd_break_deleg_cb+0xb5/0xc0 [nfsd] > 2021-05-04T02:28:21.051247+02:00 storage-t20 kernel: [1736623.921553] > __break_lease+0x148/0x500 > 2021-05-04T02:28:21.051249+02:00 storage-t20 kernel: [1736623.921564] ? > fill_pre_wcc+0x8f/0x180 [nfsd] > 2021-05-04T02:28:21.051250+02:00 storage-t20 kernel: [1736623.921566] > notify_change+0x196/0x4c0 > 2021-05-04T02:28:21.051250+02:00 storage-t20 kernel: [1736623.921575] ? > nfsd_setattr+0x2e6/0x470 [nfsd] > 2021-05-04T02:28:21.051250+02:00 storage-t20 kernel: [1736623.921586] > nfsd_setattr+0x2e6/0x470 [nfsd] > 2021-05-04T02:28:21.051251+02:00 storage-t20 kernel: [1736623.921597] > nfsd4_setattr+0x7b/0x140 [nfsd] > 2021-05-04T02:28:21.051251+02:00 storage-t20 kernel: [1736623.921611] > nfsd4_proc_compound+0x355/0x680 [nfsd] > 2021-05-04T02:28:21.051251+02:00 storage-t20 kernel: [1736623.921623] > nfsd_dispatch+0xd4/0x180 [nfsd] > 2021-05-04T02:28:21.051253+02:00 storage-t20 kernel: [1736623.921661] > svc_process_common+0x390/0x6c0 [sunrpc] > 2021-05-04T02:28:21.051253+02:00 storage-t20 kernel: [1736623.921680] ? > svc_recv+0x3c4/0x8a0 [sunrpc] > 2021-05-04T02:28:21.051254+02:00 storage-t20 kernel: [1736623.921688] ? > nfsd_svc+0x300/0x300 [nfsd] > 2021-05-04T02:28:21.051254+02:00 storage-t20 kernel: [1736623.921695] ? > nfsd_destroy+0x60/0x60 [nfsd] > 2021-
Processed: reassign 741663 to src:linux, closing 741663
Processing commands for cont...@bugs.debian.org:
> reassign 741663 src:linux 3.13.4-1
Bug #741663 {Done: John Paul Adrian Glaubitz }
[linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
Bug reassigned from package 'linux' to 'src:linux'.
No longer marked as found in versions 3.13-1.
No longer marked as fixed in versions 5.10.28-1 and 5.10.0-6.
Bug #741663 {Done: John Paul Adrian Glaubitz }
[src:linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load
correctly
Marked as found in versions linux/3.13.4-1.
> close 741663 5.10.28-1
Bug #741663 {Done: John Paul Adrian Glaubitz }
[src:linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load
correctly
Marked as fixed in versions linux/5.10.28-1.
Bug #741663 {Done: John Paul Adrian Glaubitz }
[src:linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load
correctly
Bug 741663 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
741663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
reassign 741663 to src:linux, closing 741663
reassign 741663 src:linux 3.13.4-1 close 741663 5.10.28-1 thanks
Processed: Re: Processed: Re: Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 741663 5.10.28-1
Bug #741663 {Done: John Paul Adrian Glaubitz }
[linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
There is no source info for the package 'linux' at version '5.10.28-1' with
architecture ''
Unable to make a source version for version '5.10.28-1'
Marked as fixed in versions 5.10.28-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
741663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Processed: your mail
Processing commands for cont...@bugs.debian.org:
> fixed 741663 5.10.0-6
Bug #741663 {Done: John Paul Adrian Glaubitz }
[linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
There is no source info for the package 'linux' at version '5.10.0-6' with
architecture ''
Unable to make a source version for version '5.10.0-6'
Marked as fixed in versions 5.10.0-6.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
741663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reassign 741663 linux 3.13-1
Bug #741663 {Done: John Paul Adrian Glaubitz }
[src:linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load
correctly
Bug reassigned from package 'src:linux' to 'linux'.
No longer marked as found in versions linux/3.16.7-ckt25-1.
Ignoring request to alter fixed versions of bug #741663 to the same values
previously set
Bug #741663 {Done: John Paul Adrian Glaubitz }
[linux] linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
There is no source info for the package 'linux' at version '3.13-1' with
architecture ''
Unable to make a source version for version '3.13-1'
Marked as found in versions 3.13-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
741663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#825840: marked as done (offb/ATY,RockHopper: inverts red and blue in bterm)
Your message dated Tue, 4 May 2021 15:48:28 +0200 with message-id and subject line Re: Bug#825840: Possible fix for colour invertion on ATY,Rockhopper2 has caused the Debian Bug report #825840, regarding offb/ATY,RockHopper: inverts red and blue in bterm to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 825840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-4.5.0-2-powerpc Version: 4.5.4-1 During Debian installation the background color is inverted on PPC system. At least on my Mac Mini G4, the default background color shows up as red from begining to start (only the last screen turn blue). Looking at the module loaded during the installation I can see radeonfb, which I suspect is the one responsible for handling of `/dev/fb0`. After installation I tried reproducing this color inversion without any luck so far. It is non-trivial to `rmmod radeon`, so instead I used (and rebooted): $ cat /etc/modprobe.d/radeon.conf blacklist radeon However upon reboot `/dev/fb0` is already setup. But neither radeonfb nor radeon module seems to be loaded (using lsmod) but lspci output is rather confusing [*]. I can also see: $ cat /proc/fb 0 OFfb ATY,RockHo Playing with the virtual screen with a red and blue color and `fim`, all images looks weird, I could not figure out if there was something special to setup so that I can display a red or blue image in `fim`. Lastly, I can run `dmesg` and the color looks right (error messages are displayed in red, timestamp in green). I'd like to keep this bug open until I find what is going on with this color inversion on PPC/ATI. $ lspci -s :00:10.0 -vvx :00:10.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV280 [Radeon 9200] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV280 [Radeon 9200] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel modules: radeonfb, radeon 00: 02 10 62 59 07 00 b0 02 01 00 00 03 08 ff 00 00 10: 08 00 00 98 01 04 00 00 00 00 00 90 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 02 10 62 59 30: 00 00 02 90 58 00 00 00 00 00 00 00 ff 01 08 00 --- End Message --- --- Begin Message --- Salvatore, On Sun, May 2, 2021 at 8:59 AM Salvatore Bonaccorso wrote: > > Control: tags -1 + moreinfo > > Hi Mathieu, > > This bug thread was by the time very long but stoppend in 2016. Are > the issues still relevant for us or should we close this bug by now? Thanks for your triaging. It turns out Adrian was able to release an updated d-i for debian-power. So now all mac/ppc32 that were affected with the color inversion are now loading the radeonfb driver instead of the offb one. The bug is no longer visible to users but to (long beard) developers... I am going to close it, no chance upstream will ever fix it.--- End Message ---
Bug#825840: Possible fix for colour invertion on ATY,Rockhopper2
Salvatore, On Sun, May 2, 2021 at 8:59 AM Salvatore Bonaccorso wrote: > > Control: tags -1 + moreinfo > > Hi Mathieu, > > This bug thread was by the time very long but stoppend in 2016. Are > the issues still relevant for us or should we close this bug by now? Thanks for your triaging. It turns out Adrian was able to release an updated d-i for debian-power. So now all mac/ppc32 that were affected with the color inversion are now loading the radeonfb driver instead of the offb one. The bug is no longer visible to users but to (long beard) developers... I am going to close it, no chance upstream will ever fix it.
Bug#988044: linux-image-5.10.0-0.bpo.4-amd64: Kernel panic due nfsd error: refcount_t: addition on 0; use-after-free
Package: src:linux Version: 5.10.19-1~bpo10+1 Severity: important On a virtual machine running a NFS server the following kernel panic occurs: 2021-05-04T02:28:21.051193+02:00 storage-t20 kernel: [1736623.921391] [ cut here ] 2021-05-04T02:28:21.051214+02:00 storage-t20 kernel: [1736623.921406] refcount_t: addition on 0; use-after-free. 2021-05-04T02:28:21.051215+02:00 storage-t20 kernel: [1736623.921416] WARNING: CPU: 0 PID: 675 at lib/refcount.c:25 refcount_warn_saturate+0x6d/0xf0 2021-05-04T02:28:21.051216+02:00 storage-t20 kernel: [1736623.921417] Modules linked in: binfmt_misc vsock_loopback vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock intel_rapl_msr intel_rapl_common nfit libnvdimm crc32_pclmul ghash_clmulni_intel aesni_intel libaes crypto_simd cryptd glue_helper rapl vm w_balloon vmwgfx joydev evdev serio_raw pcspkr ttm sg drm_kms_helper vmw_vmci cec ac button nfsd auth_rpcgss nfs_acl lockd grace drm sunrpc fuse configfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c crc32c_generic dm_mod sd_mod t10_pi crc_t10dif crct10dif_generic ata_generic crct10dif_pclmul crct10dif_common crc32c_intel psmouse vmxnet3 ata_piix libata vmw_pvscsi scsi_mod i2c_piix4 2021-05-04T02:28:21.051217+02:00 storage-t20 kernel: [1736623.921488] CPU: 0 PID: 675 Comm: nfsd Not tainted 5.10.0-0.bpo.4-amd64 #1 Debian 5.10.19-1~bpo10+1 2021-05-04T02:28:21.051218+02:00 storage-t20 kernel: [1736623.921488] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 2021-05-04T02:28:21.051219+02:00 storage-t20 kernel: [1736623.921491] RIP: 0010:refcount_warn_saturate+0x6d/0xf0 2021-05-04T02:28:21.051219+02:00 storage-t20 kernel: [1736623.921492] Code: 05 d8 be 3f 01 01 e8 c3 0a 40 00 0f 0b c3 80 3d c8 be 3f 01 00 75 ce 48 c7 c7 30 6c 92 86 c6 05 b8 be 3f 01 01 e8 a4 0a 40 00 <0f> 0b c3 80 3d ab be 3f 01 00 75 af 48 c7 c7 08 6c 92 86 c6 05 9b 2021-05-04T02:28:21.051220+02:00 storage-t20 kernel: [1736623.921493] RSP: 0018:b93f412b3c28 EFLAGS: 00010282 2021-05-04T02:28:21.051234+02:00 storage-t20 kernel: [1736623.921494] RAX: RBX: 9c2c913a0f80 RCX: 0027 2021-05-04T02:28:21.051236+02:00 storage-t20 kernel: [1736623.921495] RDX: 0027 RSI: 9c2d39e18a00 RDI: 9c2d39e18a08 2021-05-04T02:28:21.051237+02:00 storage-t20 kernel: [1736623.921495] RBP: 9c2c96e4f2a4 R08: R09: c0007fff 2021-05-04T02:28:21.051238+02:00 storage-t20 kernel: [1736623.921496] R10: 0001 R11: b93f412b3a30 R12: 9c2c96e4f2a0 2021-05-04T02:28:21.051238+02:00 storage-t20 kernel: [1736623.921496] R13: 9c2c375f5450 R14: 9c2cb4f9fde8 R15: 86f75300 2021-05-04T02:28:21.051244+02:00 storage-t20 kernel: [1736623.921497] FS: () GS:9c2d39e0() knlGS: 2021-05-04T02:28:21.051245+02:00 storage-t20 kernel: [1736623.921498] CS: 0010 DS: ES: CR0: 80050033 2021-05-04T02:28:21.051245+02:00 storage-t20 kernel: [1736623.921499] CR2: 7f424807d5b9 CR3: 000103084001 CR4: 007706f0 2021-05-04T02:28:21.051246+02:00 storage-t20 kernel: [1736623.921522] PKRU: 5554 2021-05-04T02:28:21.051246+02:00 storage-t20 kernel: [1736623.921523] Call Trace: 2021-05-04T02:28:21.051246+02:00 storage-t20 kernel: [1736623.921546] nfsd_break_deleg_cb+0xb5/0xc0 [nfsd] 2021-05-04T02:28:21.051247+02:00 storage-t20 kernel: [1736623.921553] __break_lease+0x148/0x500 2021-05-04T02:28:21.051249+02:00 storage-t20 kernel: [1736623.921564] ? fill_pre_wcc+0x8f/0x180 [nfsd] 2021-05-04T02:28:21.051250+02:00 storage-t20 kernel: [1736623.921566] notify_change+0x196/0x4c0 2021-05-04T02:28:21.051250+02:00 storage-t20 kernel: [1736623.921575] ? nfsd_setattr+0x2e6/0x470 [nfsd] 2021-05-04T02:28:21.051250+02:00 storage-t20 kernel: [1736623.921586] nfsd_setattr+0x2e6/0x470 [nfsd] 2021-05-04T02:28:21.051251+02:00 storage-t20 kernel: [1736623.921597] nfsd4_setattr+0x7b/0x140 [nfsd] 2021-05-04T02:28:21.051251+02:00 storage-t20 kernel: [1736623.921611] nfsd4_proc_compound+0x355/0x680 [nfsd] 2021-05-04T02:28:21.051251+02:00 storage-t20 kernel: [1736623.921623] nfsd_dispatch+0xd4/0x180 [nfsd] 2021-05-04T02:28:21.051253+02:00 storage-t20 kernel: [1736623.921661] svc_process_common+0x390/0x6c0 [sunrpc] 2021-05-04T02:28:21.051253+02:00 storage-t20 kernel: [1736623.921680] ? svc_recv+0x3c4/0x8a0 [sunrpc] 2021-05-04T02:28:21.051254+02:00 storage-t20 kernel: [1736623.921688] ? nfsd_svc+0x300/0x300 [nfsd] 2021-05-04T02:28:21.051254+02:00 storage-t20 kernel: [1736623.921695] ? nfsd_destroy+0x60/0x60 [nfsd] 2021-05-04T02:28:21.051255+02:00 storage-t20 kernel: [1736623.921710] svc_process+0xb7/0xf0 [sunrpc] 2021-05-04T02:28:21.051255+02:00 storage-t20 kernel: [1736623.921734] nfsd+0xe8/0x140 [nfsd] 2021-05-04T02:28:21.051257+02:00 storage-t20 kernel: [1736623.921737] kthread+0x
