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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 03232C5AE59 for ; Wed, 4 Jun 2025 02:54:57 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 894C66B056A; Tue, 3 Jun 2025 22:54:56 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 81D0D6B056E; Tue, 3 Jun 2025 22:54:56 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 736926B056F; Tue, 3 Jun 2025 22:54:56 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 53CB86B056A for ; Tue, 3 Jun 2025 22:54:56 -0400 (EDT) Received: from smtpin12.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id F31AEC2046 for ; Wed, 4 Jun 2025 02:54:55 +0000 (UTC) X-FDA: 83516200950.12.BA4626C Received: from nyc.source.kernel.org (nyc.source.kernel.org [147.75.193.91]) by imf09.hostedemail.com (Postfix) with ESMTP id 3FE53140003 for ; Wed, 4 Jun 2025 02:54:54 +0000 (UTC) Authentication-Results: imf09.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=fBLZKkGL; spf=pass (imf09.hostedemail.com: domain of akpm@linux-foundation.org designates 147.75.193.91 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1749005694; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=hMsbD5+NmEJXcKdRz1UY/XpCm0up98OAyulf5RvaduI=; b=otqN6DEBDYkZkntseDLhCze5gNmvteNtDBUgR9fpJoFlVbrRAo7o0uyW9cprOJ+DRcXUff 1NllPgZUzFBz5+M7Dixa2oJ2FpvBs6ycewn/Cv3vikcy1ZH9n2oxpwUy8IFzuqUu8+t1UJ 4I8l0gb+ipkLl6lqZlXt7dv1IyFin40= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1749005694; a=rsa-sha256; cv=none; b=q1IDSfzcAgW6JOntTcGK6/igIIbrPv+MWLnTfys22FHvyyIpOt581TpDhz4EHtWdIUDItV 7KPNL0OqwDQ81+LtABYYjh1kLrXDGe5K3fa0t5TiJ55sWNLT2EyKQqIbzZupEMbhcXqM2i c30L3c49J+/8yfy/8Fs8hk79TPFNdh8= ARC-Authentication-Results: i=1; imf09.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=fBLZKkGL; spf=pass (imf09.hostedemail.com: domain of akpm@linux-foundation.org designates 147.75.193.91 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id 9E5B6A4C80A; Wed, 4 Jun 2025 02:54:53 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 29866C4CEED; Wed, 4 Jun 2025 02:54:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1749005693; bh=1rlRvikIg6i8v3ujs5Nxj2v/xNHUqob6b3dIoO/LQ8Q=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=fBLZKkGLNQ+fF0edFKQT3rGXqz/Tr0PYoiuCegpOiVVhbtOmjQX2R2kblpQcDj1KC oqHoOVG0h2eDQZa8eYB7OXPGO9/xrTqWrIcnxq0I6sqXqU7ycDMzhuyJmAckIIlmUN c+GwCWNRk+mfVCzcoaznttlVOH669zOO6HPuBPBU= Date: Tue, 3 Jun 2025 19:54:52 -0700 From: Andrew Morton To: Jann Horn Cc: Muchun Song , Oscar Salvador , linux-mm@kvack.org, Lorenzo Stoakes Subject: Re: [PATCH] hugetlb: block hugetlb file creation if hugetlb is not set up Message-Id: <20250603195452.d6238ea8a37caea9e727bc73@linux-foundation.org> In-Reply-To: References: <20250528-hugetlb-nerf-v1-1-a404ca33e819@google.com> <20250602204107.177e2fdf2209b0926b5ce28e@linux-foundation.org> X-Mailer: Sylpheed 3.8.0beta1 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 3FE53140003 X-Stat-Signature: 6ydj1xedma5mb558c5yrg93x31d997kt X-Rspam-User: X-HE-Tag: 1749005694-245827 X-HE-Meta: U2FsdGVkX1+Qco07/kdjRzIajpiUU3Y4Q4Dfw1rmyZD6iBg53rLMRPlQYYWTt1Rss3qzKu/mfX9zvhGGs3Wd6caCDu9L4mKBJxccCi94B8EJcrNliE4Cvi6z1RYM7LISyLz6mbk0R6jW687AT0b0uwbx/ioLdaZdJbhBmbrskaxHRlXnSKG3z+wkWiKBNXWdZWy96OmSOMmr0xSkemPXwT9XGfoJtfFtAm+ckZyve4YduMIJnzi4zJRzoYWNiS2DDYcagcBmhXbpQAIGrqgp1POU2nl4/ErcH7GvEKBx9V+/s7giNvDyds/kgSayDH5T+hyRcTTYe1Gjo2EVElW0/AtQrxsRz363aFA1Rt8d1e08ptw8/IQAnx1NCstdqcuBMp7w0QqNHECJOFQUEaFnAzc3Q/Sb6i4s6EcLdOLjKK0CGojwSN65eI4TGnAdE+S2keUgURJbWPyoPrgUcu7wlIdOmFCMYp1Gid+X0inpottlQoEfFNQmY50WbhYVe4F91vHHUaCCkG3tL8vy35TDKqOJcxAWWw56V9OxJxLi3PQ9VdNGwHOu8BvoCveKooOCZpxPnTuQB8S6Tz3NTTjd46fpUPOPEySqPuLGLChuX3BZoF5iwhy1r4OxRA/WaaqaClklw7+lFkttgWYI1QIpIzPa6K/cDFpoj4lJaOMOleDEF0xeYjcnxIwRr1fO6VSQU+utYWv96BzsS8DfvZuuw5rs2oBW4G1rJVxbU1mussYyahuDpS184r+BaF9L8Eorzb7Ju+9QXKncnFWBRvUymGq7hK+LQUKK9Enfc6Xplqo58MhqU5ddVaCHb0rs/ZjbcTbCt98ShGhNh5hEiPsNPnrWoBo8TWROYYxqYpTSYkA7gTrLhlY9yvvVBe/Z0UaSqk4WVj+ppBZn4GSZ2Q7xW6Xxqf2l56svP3F8DeBFaktKpJIuooXFzfHwUuLn/ELM3gdcl1cjRwZcBlO6gRW 99fGcSij YEJpnMKcoooUBslllq3IsRgIDV8Qst0Hawz/3WHoXgjuOLB3D5Z9bhEQE4QT8UC+4DGcnGRujFAyaVZCCDITsc8EsqUxhNzQXrI+iTmb7vQZFmT+LW5AEN0ZamOFas8EJIJsHNXN9X4An12cxbG0Va+9OVL738FiXSWCA7v2I0U0/5raSqWSjJTT2yXkJZXhBLk2xFaYrnw3uO1bXnr3nCRiCKaiODJa6a7rWWOt4IhKzMuNGulAg7nXEtq0jyF9hocHvM+Z5UtsyjS8= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Tue, 3 Jun 2025 06:29:24 +0200 Jann Horn wrote: > I did think about whether this is the kind of borderline-breaking > change that should include a pr_warn_once() to inform the user that > their system encountered a specific behavioral difference due to a > kernel change, in case it does unexpectedly break something; I decided > against it, but if someone thinks this is sufficiently close to a > breaking change to warrant that, I'll add that. We could not make the change at this time. Instead we emit a loud "don't do this, we're taking it away" warning and see if anyone reports it. Or we could merge this change as-is, along with a warning to get people's attention then run that in -next for a while.