From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 22573 invoked from network); 10 Jan 2022 13:30:39 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 10 Jan 2022 13:30:39 -0000 Received: (qmail 5481 invoked by uid 550); 10 Jan 2022 13:30:36 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 5461 invoked from network); 10 Jan 2022 13:30:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1641821423; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Zl/cEfPYj8bZGPBCRKmgk6hMiVE2VXxty+xwCuSaDrQ=; b=jESjke7Lyf8eesrudjAFMnapJaJFZ1qCTQ9jDFQm0RNexnWBalKQfd+A4e7/axvu6mkff/ hYMiZ02msAFcW6Td/X46TpX0gb26Yjvia/4UGZNBERojHRWMht0eoSIt1M+SpSF2Gtlq0m QCDeRW4J/LNkmmfyR7E1VVguxpdqHaw= X-MC-Unique: m-LIV4qNPF-M6k5sLuiB3Q-1 From: Florian Weimer To: Rich Felker Cc: Nihal Jere , musl@lists.openwall.com References: <20220104214211.GC7074@brightrain.aerifal.cx> <8735m2ftmu.fsf@oldenburg.str.redhat.com> <20220105134957.GF7074@brightrain.aerifal.cx> <87pmp6e0yy.fsf@oldenburg.str.redhat.com> <20220105150035.GG7074@brightrain.aerifal.cx> <87v8yv3aw1.fsf@oldenburg.str.redhat.com> <20220107173536.GK7074@brightrain.aerifal.cx> Date: Mon, 10 Jan 2022 14:30:17 +0100 In-Reply-To: <20220107173536.GK7074@brightrain.aerifal.cx> (Rich Felker's message of "Fri, 7 Jan 2022 12:35:38 -0500") Message-ID: <87iluryaza.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=fweimer@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: Re: [musl] Dynamic linker segfault * Rich Felker: > By my understanding, p_align implies an understanding by the creator > of the program that the load segment may be "over-mapped" (extra file > contents visible and possibly executable) up to that alignment > boundary due to page granularity. This isn't really a correctness > contract but a security/hardening contract for folks who consider > anti-ROP measures a boundary that should be enforced. Not sure if I follow. Do you mean p_align is purely for documenting layout decisions by the link editor? I suspect that the necessary overlap would be visible by other means, too. Thanks, Florian