linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: Alexey Dobriyan <adobriyan@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Willy Tarreau <w@1wt.eu>,
	Dan Carpenter <dan.carpenter@oracle.com>,
	Kees Kook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org
Subject: process '/usr/bin/rsync' started with executable stack
Date: Tue, 23 Jun 2020 10:39:26 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.22.1.446.2006231023390.3892@trent.utfs.org> (raw)

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, 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. 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?

Please advise? :-)

Thanks,
Christian.

[0] https://lore.kernel.org/patchwork/patch/1164047/#1362722


$ checksec --format=json --extended --file=`which rsync` | jq
{
  "/usr/bin/rsync": {
    "relro": "full",
    "canary": "yes",
    "nx": "no",
    "pie": "yes",
    "clangcfi": "no",
    "safestack": "no",
    "rpath": "no",
    "runpath": "no",
    "symbols": "no",
    "fortify_source": "yes",
    "fortified": "10",
    "fortify-able": "19"
  }
}

-- 
BOFH excuse #244:

Your cat tried to eat the mouse.

             reply	other threads:[~2020-06-23 17:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 17:39 Christian Kujau [this message]
2020-06-23 18:32 ` process '/usr/bin/rsync' started with executable stack 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
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=alpine.DEB.2.22.1.446.2006231023390.3892@trent.utfs.org \
    --to=lists@nerdbynature.de \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).