public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Willy Tarreau <w@1wt.eu>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Kees Kook <keescook@chromium.org>,
	linux-kernel@vger.kernel.org
Subject: Re: process '/usr/bin/rsync' started with executable stack
Date: Wed, 24 Jun 2020 00:22:14 +0300	[thread overview]
Message-ID: <20200623212214.GA41702@localhost.localdomain> (raw)
In-Reply-To: <20200623211218.GA40110@localhost.localdomain>

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.

  reply	other threads:[~2020-06-23 21:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 17:39 process '/usr/bin/rsync' started with executable stack Christian Kujau
2020-06-23 18:32 ` Kees Cook
2020-06-23 21:33   ` Christian Kujau
2020-06-23 21:41     ` Alexey Dobriyan
2020-06-23 21:45     ` Alexey Dobriyan
2020-06-23 21:50     ` Alexey Dobriyan
2020-06-23 22:02       ` Christian Kujau
2020-06-23 21:12 ` Alexey Dobriyan
2020-06-23 21:22   ` Alexey Dobriyan [this message]
2020-06-23 21:51     ` Christian Kujau
2020-06-23 23:20     ` Kees Cook
2020-06-24  5:34       ` Christian Kujau
2020-06-24 16:51 ` Dan Carpenter
2020-06-24 19:39   ` Kees Cook
2020-06-25 10:04     ` Dan Carpenter
2020-06-25 20:20       ` Kees Cook
2020-06-25 21:16         ` [klibc] " Thorsten Glaser
2020-06-25 22:01           ` Kees Cook
2020-06-26  4:42         ` Christophe Leroy
2020-07-25 21:27         ` Ben Hutchings
2020-07-26  2:07           ` Kees Cook

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200623212214.GA41702@localhost.localdomain \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox