On Wed, Jun 24, 2020 at 12:12:18AM +0300, Alexey Dobriyan wrote: > On Tue, Jun 23, 2020 at 10:39:26AM -0700, Christian Kujau wrote: > > Hi, > > > > exactly this[0] happened today, on a 5.6.5 kernel: > > > > process '/usr/bin/rsync' started with executable stack > > > > But I can't reproduce this message,
This message is once-per-reboot. If you run something with exec stack after the message you shouldn't get it second time. If you rebooted and rsync starts clean, then it is separate story. > > and rsync (v3.2.0, not exactly > > abandonware) runs several times a day, so to repeat Andrew's questions[0] > > from last year: > > > > > What are poor users supposed to do if this message comes out? > > > Hopefully google the message and end up at this thread. What do you > > > want to tell them? > > > > Also, the PID is missing from that message. > > That's intentional. I for one hate pids. > > > I had some long running rsync > > processes running earlier, maybe the RWE status would have been visible in > > /proc/$PID/map, or somewhere else maybe? > > If you think process is still running, /proc/*/maps should have 'rwxp' > indeed. You can do quick > > $ grep -e '\[stack\]' /proc/*/maps' > > to find it. Run as root obviously, or you won't get full picture.
