Bug 29576

No evident maintainer in sight, so assigning this globally.

Assignee: bugsquad => pkg-bugs

Hi,

I cannot find the code that causes the issue in version 5.15.

Best regards,

Nico.

CC: (none) => nicolas.salguero

There is a realloc call in src/mount.c, but I don't know if it has the same issue.

can we update to 5.16 in mga8/9 ?

CC: (none) => mageia

It looks like 5.16 also fixed a buffer overflow, so it sounds like a good idea.

updated in cauldron and mga8:

src:
    - watchdog-5.16-1.mga8

Assignee: pkg-bugs => qa-bugs
Version: Cauldron => 8
Status comment: Patch available from Fedora => (none)
Whiteboard: MGA8TOO => (none)

MGA8-64 Plasma on Lenovo B50 in Dutch
No installation issues.
No wiki, no previous updates, so went googling and found https://linuxhint.com/linux-kernel-watchdog-explained/
So went on and dived in the deep
#  systemctl  start watchdog
#  systemctl -l status watchdog
● watchdog.service - watchdog daemon
     Loaded: loaded (/usr/lib/systemd/system/watchdog.service; disabled; vendor preset: disabled)
     Active: active (running) since Tue 2021-12-14 15:23:31 CET; 4s ago
    Process: 8872 ExecStart=/usr/sbin/watchdog (code=exited, status=0/SUCCESS)
   Main PID: 8874 (watchdog)
      Tasks: 1 (limit: 9396)
     Memory: 588.0K
        CPU: 4ms
     CGroup: /system.slice/watchdog.service
             └─8874 /usr/sbin/watchdog

dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  file: no file to check
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  pidfile: no server process to check
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  interface: no interface to check
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  temperature: no sensors to check
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  no test binary files
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  no repair binary files
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  error retry time-out = 60 seconds
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  repair attempts = 1
dec 14 15:23:31 mach5.hviaene.thuis watchdog[8874]:  alive=[none] heartbeat=[none] to=root no_act=no force=no
dec 14 15:23:31 mach5.hviaene.thuis systemd[1]: Started watchdog daemon.

My laptop keeps running normally, that's good!!!!
OK'ing unless someone has a better idea.

CC: (none) => herman.viaene
Whiteboard: (none) => MGA8-64-OK

The website you cited does give an easy-sounding test procedure:

Testing the Watchdog

If you want to test if the hardware watchdog is working, you can do the following from your administrator command prompt:
cat >> /dev/watchdog

And press “enter” twice and wait. The prompt will not come back. After awhile depending on your kernel’s setting, the system should perform the hard reboot.

Care to try that? If you'd rather not risk it for some reason, I can try it on one of my test installs.

CC: (none) => andrewsfarm

That"s the most scary test I ever did. This indeed provokes a reboot, and the system boots OK (writing on it now). Watchdog was inactive, so I hurried to get rid of it.

That's why I said I'd be willing to try it on a test install - something I'd be willing to lose if things went awry. I always keep one or two of those available. 

The article does say "Personal computer users don’t need watchdog as they can reset the system manually," so I too would have removed it promptly after doing the test.

Thanks for taking the risk. Validating.

CC: (none) => sysadmin-bugs
Keywords: (none) => validated_update

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2021-0569.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED