From nobody Tue Oct 18 11:48:11 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MsBvM1297z4fMBm for ; Tue, 18 Oct 2022 11:48:15 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MsBvL2bf4z41vx for ; Tue, 18 Oct 2022 11:48:14 +0000 (UTC) (envelope-from paulf2718@gmail.com) Received: by mail-wr1-x430.google.com with SMTP id a3so23114260wrt.0 for ; Tue, 18 Oct 2022 04:48:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=QXY4zV2mivtjer2wTk4afF5d4lW2TAdcj9u2IQm3TpU=; b=BYY0Z1szIkWISrWq4n1gN+8XCkgbCGqYVuqlo4m0NWS1OD/zOTAxPEKQ5KIgB+w+0H WvEkHBETdYVSsKjaPkUC5d8de1JuxVqJCcw/yP2ZcukhR+8jxhVlByyVw6oOvX9lsmKv n6WhaMuNV9wyYDXcvlYIf+AezHSZ7ZmVpjyWtJ0zRqSgRZ82ZB/DM7K50LS8c0dxnQxL zKKdXUPu0Y7XzQizq20Xy2aE1ekv4vCrVK2BnGoVcMTSMubfeLcagaQ22qPavSCgB8EW OIJdCw8io5GQzeHnBQC68rDgmNUGgtWYYQ+r7HQQVIDZwmDAAT3mFXaL/V8OqSrCeOxe v/ZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=QXY4zV2mivtjer2wTk4afF5d4lW2TAdcj9u2IQm3TpU=; b=4JLTubdtkyQATdwk1oW/5JYiWM9DiQh4VjwACPxs3FyutZ0/DrDU0rgrr4zT8uOorN bkWsdTypSjTVdjVjD3YW3NUOTrR8+7CvFWRtwYFDxubPC4BZf7WqyGdQU+BITsxu7h6j ebeOmryjN83AMzECy8XHJOeQ/eqNI6sFNVEJJ5hxHrxuJTwGJBMUzNAvD5f2kuN/Ua0A 2N4e6wyKKrBy1kss467oBQm3Kp+xvQprcHGuAVCh1eMY4PGfVm/EsEalep1uv4Ex4HHf Vzn6YTuKXFbwkEJpLbiCId1ZGq3HgE2GyEoeeg162/kPI9eMf7z2d3at7RTTgsuICrGp uVVA== X-Gm-Message-State: ACrzQf25HsnA/kn5pWTkyRYQdzjHbOsAMkix3iJvIAHPDkWAaIQsFdpv Hq5tEmqTCt7OKDcIad3nXVthdrFmfGuKpA== X-Google-Smtp-Source: AMsMyM6goccUOvoaiTLZeSjzi69vq/cWicBBWtSFBXCuEfXZ2XP7PGn3a0Rk92CiSsOiS3vHLu940w== X-Received: by 2002:a5d:6504:0:b0:22e:44b0:4cf5 with SMTP id x4-20020a5d6504000000b0022e44b04cf5mr1589665wru.362.1666093692771; Tue, 18 Oct 2022 04:48:12 -0700 (PDT) Received: from [192.168.1.28] (lfbn-lyo-1-263-217.w2-7.abo.wanadoo.fr. [2.7.103.217]) by smtp.gmail.com with ESMTPSA id a19-20020a05600c225300b003a6a3595edasm13375664wmm.27.2022.10.18.04.48.12 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 18 Oct 2022 04:48:12 -0700 (PDT) Message-ID: <578a011d-0c3f-3f91-48ca-17999a6515a9@gmail.com> Date: Tue, 18 Oct 2022 13:48:11 +0200 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.3.2 Subject: Re: AMD64 14.0-CURRENT memory layout changes To: freebsd-hackers References: Content-Language: en-US From: Paul Floyd In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4MsBvL2bf4z41vx X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=BYY0Z1sz; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of paulf2718@gmail.com designates 2a00:1450:4864:20::430 as permitted sender) smtp.mailfrom=paulf2718@gmail.com X-Spamd-Result: default: False [-3.93 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.93)[-0.929]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_TLS_LAST(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::430:from]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-ThisMailContainsUnwantedMimeParts: N Hi Mark > Setting kern.elf(64|32).aslr.stack to 0 should restore the old > behaviour. It should also be possible to disable this on a per-process > basis with proccontrol(1), but that doesn't appear to work, i.e., there > is a bug. However, all randomization can be disabled this way, try > "procstat -m aslr -s disable ksh93". If I turn off all aslr then I do see that the memory map reverts to the same layout as I get in 13.1. But that doesn't solve my problems. I've also seen that sysctl kern.usrstack is no longer used. On 13.1 I see PID trylock CALL __sysctl(0x7fffffffd310,0x2,0x800267c88,0x7fffffffd328,0,0) PID trylock SCTL "kern.usrstack" PID trylock RET __sysctl 0 PID trylock CALL getrlimit(RLIMIT_STACK,0x7fffffffd318) PID trylock RET getrlimit 0 PID trylock CALL thr_self(0x800a12000) PID trylock RET thr_self 0 PID trylock CALL mmap(0x7fffdfffe000,0x1000,0,0x1000,0xffffffff,0) PID trylock RET mmap 140736951476224/0x7fffdfffe000 But on 14.0 I think that this is the mmap for rtld PID trylock CALL mmap(0,0x400000,0x3,0x15001002,0xffffffff,0) PID trylock RET mmap 34372321280/0x800c00000 PID trylock CALL thr_self(0x800a12000) PID trylock RET thr_self 0 then straight to mapping the stack PID trylock CALL mmap(0x7fffdfffe000,0x1000,0,0x1000,0xffffffff,0) PID trylock RET mmap 140736951476224/0x7fffdfffe000 How is 14.0 working out what address to use for the stack? (The above is with ASLR all off) A+ Paul