From nobody Fri Jul 15 22:32:21 2022 X-Original-To: freebsd-current@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 4Ll5hT6WKRz4WpMV for ; Fri, 15 Jul 2022 22:32:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (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 4Ll5hT2RXlz49fj for ; Fri, 15 Jul 2022 22:32:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qv1-xf35.google.com with SMTP id g9so4692965qvq.7 for ; Fri, 15 Jul 2022 15:32:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=O0xH74SrkYc7Wd08R1hd1WUHfdCbmQF5t3szbIlXlxU=; b=FLwXs0PR9QsbGUBXsl7DwUQZGHnNUMg4zqqebpnNL4K3dHupXgxWiwFhkUzYatzXIP akGVZvC52ukWZFG8WCE+6O8F8V3WlemyjF77YmWpaRAuczXkRmclS2dESGZeHQQL6Zow HplnTFRsWbRexmlQUPtv0uMNF1Aex/OT3YQZ4fEJ9/boITcj6GCeXT/r/PLurIo7DjdK c8I8humANPRtJR/9+TeioJPm6O10a+c3olFgvHuY+P8qtLV6Xtuvl473BS+ahzaBVRvE KGa1c061fUoMidDvIutgJiBb8hS62kCByp4sqWEN9MWiV8i0IBGt+uG4htGQtFc0cRtg gQdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to; bh=O0xH74SrkYc7Wd08R1hd1WUHfdCbmQF5t3szbIlXlxU=; b=HjfXeGlt+AzEwRJxUvQxwQ1d/CDtaKYInxV/91tgQrZ+lWd4GWXJOlGP6JNTJ1+zJ7 7p1A5t4N0U1q9CZ/iwPzwuCodoWkkEtDXdsxWdug7QvolTbf5covjV06JQyeF5X1KkoQ xA6FnnYjBf6Q3Vu6AznfswJ8jBBzWoE2yViomR5q1UjsX/aGBw1hkJ9GBEza7ZJuJPCG ZPYPSlpMNkmUO77fmczY18s6x1kJyxe9skUAHPBBSSQZPnKTmhuzpoSwoc16S4usMSkU g+/JXFCPgEvvFFTpvx1v70c9n3SuRhNg/XWMi9JKjBA7zNTlxlqrTnEa7QeZOGmXEXyy fLlg== X-Gm-Message-State: AJIora9aK/QF56f5howNIhB2XQ+tKoaa8XOvvWiMjDzORz+mG5r5wU74 cIu3WPdDon+E3+EXYMpRmpO3RBxc1bE= X-Google-Smtp-Source: AGRyM1tDii4BHPf5wwDpWM2D0Qx4gVg7+k+iBTktUpkvVuL1/SDf8MfWmfN+GjRcTzRbe8s7vamPIg== X-Received: by 2002:a05:6214:2268:b0:473:1196:c599 with SMTP id gs8-20020a056214226800b004731196c599mr13579795qvb.14.1657924344731; Fri, 15 Jul 2022 15:32:24 -0700 (PDT) Received: from nuc (192-0-220-237.cpe.teksavvy.com. [192.0.220.237]) by smtp.gmail.com with ESMTPSA id w3-20020a05620a444300b006b58aa4e0e0sm3584149qkp.24.2022.07.15.15.32.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Jul 2022 15:32:24 -0700 (PDT) Date: Fri, 15 Jul 2022 18:32:21 -0400 From: Mark Johnston To: Larry Rosenman Cc: Freebsd current Subject: Re: limits.conf/stacksize doesn't seem to work? Message-ID: References: <32dc6f5b56a749f9b8e26330f9f2e8e0@lerctr.org> <51ef4fe0c8c5bbe251d3e75084847a6e@lerctr.org> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <51ef4fe0c8c5bbe251d3e75084847a6e@lerctr.org> X-Rspamd-Queue-Id: 4Ll5hT2RXlz49fj X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=FLwXs0PR; dmarc=none; spf=pass (mx1.freebsd.org: domain of markjdb@gmail.com designates 2607:f8b0:4864:20::f35 as permitted sender) smtp.mailfrom=markjdb@gmail.com X-Spamd-Result: default: False [-1.70 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; MID_RHS_NOT_FQDN(0.50)[]; FORGED_SENDER(0.30)[markj@freebsd.org,markjdb@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::f35:from]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DMARC_NA(0.00)[freebsd.org]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MLMMJ_DEST(0.00)[freebsd-current]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[markj@freebsd.org,markjdb@gmail.com]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; RCVD_VIA_SMTP_AUTH(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Fri, Jul 15, 2022 at 05:26:09PM -0500, Larry Rosenman wrote: > On 07/15/2022 5:24 pm, Mark Johnston wrote: > > On Fri, Jul 15, 2022 at 05:21:27PM -0500, Larry Rosenman wrote: > >> On 07/15/2022 5:18 pm, Mark Johnston wrote: > >> > On Fri, Jul 15, 2022 at 05:04:18PM -0500, Larry Rosenman wrote: > >> >> I'm using the following kernel config: > >> >> [...] > >> >> and the following login.conf: > >> >> [...] > >> >> bacula_dir:\ > >> >> :stacksize-max=68719476736:\ > >> >> :stacksize-cur=68719476736:\ > >> >> :tc=daemon: > >> >> [...] > >> >> I've updated my (ler) password entry to reference bacula_dir: > >> >> ler::1001:1001:bacula_dir:0:0:Larry > >> >> Rosenman:/home/ler:/usr/local/bin/zsh > >> >> > >> >> > >> >> when I ssh in, the stacklimit is still: > >> >> โฏ ulimit -H -s > >> >> 2097152 > >> > > >> > What is the value of the kern.maxssiz sysctl on this system? > >> > > >> >> ler in ๐ŸŒ borg in sys/amd64/conf๐Ÿ”’ on ๎‚  ler/freebsd-main-changes:main on > >> >> โ˜๏ธ (us-east-1) > >> >> โฏ ulimit -S -s > >> >> 2097152 > >> >> > >> >> ler in ๐ŸŒ borg in sys/amd64/conf๐Ÿ”’ on ๎‚  ler/freebsd-main-changes:main on > >> >> โ˜๏ธ (us-east-1) > >> >> โฏ > >> >> > >> >> Where does this number come from? What am I missing here? > >> > > >> > The stack limit cannot be set to an arbitrarily large number. It will > >> > silently be clamped to maxssiz. > >> > >> โฏ sysctl kern.maxssiz > >> kern.maxssiz: 2147483648 > > > > Then what you're seeing is expected. The kernel is clamping the stack > > segment limit to 2GB. > > I assume this is the default for MAXSSIZ? and if I change that in the > kernel config, it will > allow bigger? Where is this default defined? The default value is platform dependent. On amd64 it's 512MB, so I'm not sure where your value is coming from. It's defined in a header. You can set it in the kernel configuration, or as a tunable or sysctl.