From owner-freebsd-current@freebsd.org Thu Aug 20 06:33:39 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D41753B278F for ; Thu, 20 Aug 2020 06:33:39 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) (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 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4BXFGV3PPyz3gqd for ; Thu, 20 Aug 2020 06:33:38 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm1-x333.google.com with SMTP id 3so585508wmi.1 for ; Wed, 19 Aug 2020 23:33:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:reply-to :mime-version:content-transfer-encoding; bh=CfwGBRL0cbkR7oEFz8nRFUNr3RrUVr2uGbOasQ3Sxeg=; b=NrZr/WvOIIxx32fj1WlviZQZknrxoubEAOSo7KxciPPeLCDHtkkRWYEK7z0U++mDAh kMsuKXCdmXEqnM9oUTYttuLslPDc51Jy6rW2h36kIFzflbvPQ9E9TM3xBA6TEFNJNOoe nun4mzb44b7mKkALJcx/sDJYCw1M4l94dgbD7rCz1XttG/gRlLqGHSJJq6NWnedLRNCm v3TQR9/qs60HxHM033r6iQJGR2MrSAyFpaOgyXhd4RCy8mYiKn4b+JUzMItmCRHVfZGd qvVoEHXrUKshpsurN6E1JQgqua8M8A1+gmivis65aQIMDoSvLzEyFl+PngkQ767xJON7 PGGQ== X-Gm-Message-State: AOAM532Fm+bkQtAGXrSSnYq8CV892dwb8cjjxFwth2vF3bw7eiLQM1DI SvcyRffXwEJivVOeERiUzd5qh5uf0es= X-Google-Smtp-Source: ABdhPJzNGSGhevyckyaD2DWWyJvaER6mqWcGVREgpHmw//Ghs+ODPYIiLpyv2Ecxn2vvFw9b9xuhvw== X-Received: by 2002:a1c:cc05:: with SMTP id h5mr1802541wmb.129.1597905216295; Wed, 19 Aug 2020 23:33:36 -0700 (PDT) Received: from ernst.home (pd9e23482.dip0.t-ipconnect.de. [217.226.52.130]) by smtp.gmail.com with ESMTPSA id f16sm2150898wro.34.2020.08.19.23.33.34 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Aug 2020 23:33:35 -0700 (PDT) Date: Thu, 20 Aug 2020 08:33:32 +0200 From: Gary Jennejohn To: freebsd-current@freebsd.org Subject: PRINTF_BUFR_SIZE dangerous? Message-ID: <20200820083332.59d7fbbb@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.17.5 (GTK+ 2.24.32; amd64-portbld-freebsd13.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4BXFGV3PPyz3gqd X-Spamd-Bar: / X-Spamd-Result: default: False [-0.30 / 15.00]; HAS_REPLYTO(0.00)[gljennjohn@gmail.com]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.34)[-0.339]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20161025]; RECEIVED_SPAMHAUS_PBL(0.00)[217.226.52.130:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.04)[0.039]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_REPLYTO(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::333:from]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Aug 2020 06:33:39 -0000 It seems like PRINTF_BUFR_SIZE is a kernel fault waiting to happen. Only /usr/src/sys/cam/cam_xpt.c asserts that it's <= a maximum value of 512 bytes. /usr/src/sys/kern/tty.c uses it to malloc space without checking its size. /usr/src/sys/dev/xen/console/xen_console.c and /usr/src/sys/kern/subr_prf.c blindly use it to allocate a buffer on the kernel stack. /usr/src/sys/geom/geom_subr.c and /usr/src/sys/geom/geom_io.c check whether it's defined and set it to 64 if it isn't. Otherwise it's simply used to allocate a buffer on the kernel stack. A user who doesn't really understand the purpose of PRINTF_BUFR_SIZE might think "the bigger the better" and set it to be multi-megabytes in size. I may be paranoid, but it seems like PRINTF_BUFR_SIZE should be checked everywhere the way that cam_xpt.c does it. -- Gary Jennejohn