From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 97BF4C433E0 for ; Tue, 23 Jun 2020 17:39:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7D02220781 for ; Tue, 23 Jun 2020 17:39:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387886AbgFWRjf (ORCPT ); Tue, 23 Jun 2020 13:39:35 -0400 Received: from trent.utfs.org ([94.185.90.103]:44768 "EHLO trent.utfs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387586AbgFWRjc (ORCPT ); Tue, 23 Jun 2020 13:39:32 -0400 Received: from localhost (localhost [IPv6:::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by trent.utfs.org (Postfix) with ESMTPS id A730F5FA38; Tue, 23 Jun 2020 19:39:26 +0200 (CEST) Date: Tue, 23 Jun 2020 10:39:26 -0700 (PDT) From: Christian Kujau To: Alexey Dobriyan , Andrew Morton , Willy Tarreau , Dan Carpenter , Kees Kook cc: linux-kernel@vger.kernel.org Subject: process '/usr/bin/rsync' started with executable stack Message-ID: User-Agent: Alpine 2.22.1 (DEB 446 2020-06-13) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.