On Wed, 24 Jun 2020, Alexey Dobriyan wrote: > > > process '/usr/bin/rsync' started with executable stack > > > But I can't reproduce this message, > > This message is once-per-reboot.
Interesting, thanks. Now I know why I cannot reproduce this. I still wonder what made rsync trigger this message today. The machine is running for some weeks, rsync is run a few times an hour the whole day, regularly and automatically, with always the same parameters. But oh, now I see, rsync had been upgraded (automatically) over night: > [ALPM] upgraded rsync (3.1.3-3 -> 3.2.0-1) And indeed, the _older_ version had NX enabled: $ wget https://archive.archlinux.org/packages/.all/rsync-3.1.3-3-x86_64.pkg.tar.zst $ zstd -dc rsync-3.1.3-3-x86_64.pkg.tar.zst | tar -xf - usr/bin/rsync $ checksec --format=json --extended --file=usr/bin/rsync | jq { "usr/bin/rsync": { "relro": "full", "canary": "yes", "nx": "yes", "pie": "yes", "clangcfi": "no", "safestack": "no", "rpath": "no", "runpath": "no", "symbols": "no", "fortify_source": "yes", "fortified": "10", "fortify-able": "19" } } So, while I still think a PID would have been nice, now I know that it's pr_warn_once and won't be printed again until after the next reboot. Going to ask the Arch folks why NX has been disabled... Thanks, Christian. -- BOFH excuse #211: Lightning strikes.
